Hi Andrea,
I suggest to take a look at the 'Maximum RPM' book
(http://www.redhat.com/docs/books/max-rpm/index.html) - it is now
available to read on line. It is a bit out of date but you can still
make use of it.
One difference is the split of 'rpm' and 'rpm-build', in the olden days
there was just 'rpm' ;)
I have used RPM a fair bit (both as a user & writing packages) and to be
honest I think some of the critisicm people have agianst it are a much
to do with poor packaging rather than the tool itself. The worst
'offence' is some packages claiming to require version x.y.z of another
package (or library), when what they really need is version >= x.y.z.
This is a combination of lazyness on the part of the person packaging
the software and RPM trying to be helpful by listing dependancies found
when doing the build.
You could package your application into an RPM, so it is managed like
the rest of the system.
Regards
Phil Q
Andrea Gasparini wrote:
Phil Quiney spiffera, alle venerdì 19 dicembre 2008 circa:
This location is retained
in the database. The MV packages all go under /opt/<someplace>/... by
default - just do an 'mvl-edition-rpm -qi' on a package (or
mvl-edition-rpm -pqi on the rpm file itself), the prefix is displayed as
part of the information. On the target the rpms can be installed
correctly by specifying '--prefix /'.
Ok, understood, thanks.
That prove I should study better rpm packages, as they're not yet under my
complete control. ;)
As you have simply copied the 'complete' file system for your test, I
think you will find you have removed the GTK files from the original
installation area since the RPM database will have the original
locations for the files.
That's not on the 'default' location, so it shouldn't have removed
anything. Cool. :)
Thanks again.
Byebye!
_______________________________________________
Davinci-linux-open-source mailing list
[email protected]
http://linux.davincidsp.com/mailman/listinfo/davinci-linux-open-source
