Skip to content

Conversation

@Fantomatic
Copy link

It's making possible to generate rpm based on an install directory.
qibuild genrpm have 2 external dependencies : tar and rpm.
You are able to not specify a .spec file and it will generate a default one. It will use the default one path the second time, if you still doesn't specify it.
The syntax is :
qibuild genrpm -i INSTALL -s SPECFILE

…n install directory.

Have 2 external dependencies : tar and rpm.
@dmerejkowsky
Copy link
Contributor

Hum. I do not see how this is better that calling qibuild install in a spec file. The rspec you generate depends on a 'install.tbz2' file that is not standard.

If all you want to do is to create a "quick'n'dirty' rpm so that you can keep track of what has been installed on your system, simply use checkinstall: http://asic-linux.com.mx/~izto/checkinstall/

@Fantomatic
Copy link
Author

Well, it wasn't my intention. We have very different purpose and request about our project, so i understand that you don't share this one. Anyway, how the install.tbz isn't standard ? isn't it just a tar from an install directory?
We will just fork and add our own tool that we need, that will be easier :)

@dmerejkowsky
Copy link
Contributor

Can one of the admins verify this patch?

@alkino alkino added the qibuild label Dec 8, 2015
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants