rh-lab-q/rpg

RPG is tool, that guides people through the creation of a RPM package

rpg's Issues

Add package to the list like main package name

switch Requires and Scriplets screen

Requires window should be first so we can run project build using checkinstall in the background while user is filling scriplets form.

Make import field normal CSS

Not to jump on change

connect fields with RPG API

push gui files

implement methods of SourceLoader

implement CoprUploader methods

Now you have more research oriented task:

• see what parameters are needed to build package in COPR (login on fedoraproject, srpm, ...)
• implement method in CoprUploader.upload(?) that will take the needed stuff from previous step and return True if the SRPM was uploaded and builded correctly, False otherwise.
• implement Base.upload_to_copr(token or login + pass) - it will internally get Base.srpm_path

refs:
https://fedorahosted.org/copr/wiki/UserDocs
http://miroslav.suchy.cz/blog/archives/2013/12/29/how_to_build_in_copr/
http://copr-fe-dev.cloud.fedoraproject.org/api/

add hints above labels

When you put mouse over label, it could show question mark instead of arrow and show hint. What do you think? @auchytil @eskultety @boyks

implent find_translation plugin

prepend "-f %{name}.lang" to spec.files if you find *.mo files in directory

validate that import path exists before moving to next screen

In beginning page: since there is writable input field we want to make sure that dir exists. You can use red borders from #39

port to qt4

implement PluginEngine

make one button for importing (folder + archive)

refactor Base paths and plugin phases

dirs in base class:

• extracted_dir
• patched_dir
• project_build_dir
• install_dir
• package_build_dir

plugin phases:

• init
• extracted
• patched
• compiled
• installed
• package_builded

Move documentation files to patches

Let user import directory not only archive

in beginning page

Make normal default text for scripts etc.

reorder screens

change this order:
beginning script_page patches requires scriplets subpackages documentation build
to this (with Base method calls):
beginning <process_archive_or_dir; run_raw_sources_analysis> patches <apply_patches; run_patched_sources_analysis> script_page requires <build_project; run_compiled_analysis> <install_project; run_installed_analysis> subpackages scriplets documentation build <build_packages>

add CMakeLists.txt files to the project

install files correctly
generate documentation
add cmake requires
connect cmake with nosetests

add demo functionality to Spec class

implement Command class

it will be part of Spec. Purpose of this is to represent bash commands in Spec scripts and execute them.
Plugins will append cmdlines. Base RPG class will execute command when moving to next phase.
Command could be internally represented as list of ((lists of strings) or strings)

class Command:
def __str__(self) # join command lines together. Returns one string that will be saved in spec file
def append_cmdline(self, cmdline) # adds cmdline at the end of command sequence
def execute(work_dir) # executes command in working directory

# this should be possible to do:
com = Command()
com.append_cmdline(["cd", build_dir])
com.append_cmdline("cmake ..")
com.execute(cur_dir)
str(com) # -> "cd <build_dir>\ncmake .."

add setup_workspace to Base class

It will ensure all folders for phases exist
Moreover it will compute hash of path

prefill fields from spec class

Refactor ProjectBuild

Project build will only build or install files into desired directory, other stuff will do plugins.
add to plugins:

• find_files
• cmake <- add spec.tags["build"]
• autotools <- add spec.tags["build"]
• apply_patches

ProjectBuilder new API:

• build(patched_dir, build_dir, build_commands) # throws RpgBuildError("err_str") when error occurs
• install(build_dir, install_dir, install_commands) # throws RpgInstallError("err_str") when error occurs

implement autotools plugin

depends on #11
the plugin should:

• set spec.build, spec.install
• append spec.required_files, spec.buildrequired_files

Patch ordering

Patches created with git contain a header in this format:

From 0434683 Mon Sep 17 00:00:00 2001
From: Jan Silhan [email protected]
Date: Tue, 5 Aug 2014 11:25:07 +0200
Subject: [PATCH 1/2] changed doc of plugin_engine according to new plugin API

So that brings an idea of sorting by "Date" then by "Subject".

try build libsolv package with RPG

follow the process of RPG (all the phases: see /tmp/rpg-*) and watch warnings -> add issues/fix it
the testing project is libsolv project folder

Make plugin

Implement Make plugin.

Guide to plugins

I think, that a simple guide "how should the plugins look like" would be quite useful, even for the potential community.

implement python plugin

This plugin will append dependencies based on Python files analysis. It will be analogue to C plugin. You have to figure out regexp that would parse import statements or use Python builtin ATD? parser.
depends on #11

Remove duplicity in list of files (subpackages) after return

implement methods fo ProjectBuilder

implement guess_* methods from Predictor

feel free to take it when you have nothing else to do.

implement java plugin

look how java files are packed into rpm package and where are stored on the system. Then implement plugin. Depends on #11.
the plugin should:

• set spec.build, spec.install
• append spec.required_files, spec.buildrequired_files

implement find_file plugin

It will add to spec.files = all found files in current_dir. The string path should be relative to current_dir.

implement find_library plugin

add to spec.scripts["postun/post"] = "-p /sbin/ldconfig". Look at find_patch.py for inspiration

implement cmake plugin

depends on #11

implement Spec.load method

implement find_patches plugin

implement new Spec API

see: origin/erik (51ed6a4), refactor spec class to make the tests pass

git fetch origin
git reset --hard origin/erik
git rebase origin/master

Maybe the tests are wrong so consult it with me if some misunderstanding occurs.

Tests for plugins(file, translation, library)

add commandline argparse support

--plugin-dir <dir> - will load all plugins nested within dir
--disable-plugin <plugin_name> - plugin named plugin_name will not be executed during phases

implement c plugin

depends on #11

Create a logo

We should create a logo, that would represent our project and appear in an all-apps menu.

Input field validation according to Fedora packaging guide

There should be new module with regexps for each tag. See https://fedoraproject.org/wiki/How_to_create_an_RPM_package

add checkbox for BuildArch: noarch into scripts page

and set it into spec.tags["BuildArch"] = "noarch" if checked

implement logging setup and log important parts in components

look at dnf code how logging is done. + Add log info to each component public method call + log executing of plugins in plugin_engine.

make some fields required

Name, Summary, Version, Release, License, Source

Rename Command method.

I'd suggest renaming "append_cmdlines" to just "append".
In my opinion "cmd.append" looks better than "cmd.append_cmdlines".

Feel free to assign me to this issue or to close it.

add demo functionality to PackageBuilder