On Fri, Jun 22, 2007 at 03:10:29PM -0600, Bob Proulx wrote: > In this case of people trying to use rpm for closed sourced projects > then usually the files will be installed by methods outside of rpm. The only difference between open and closed source here is that the "source" files (rpm speak) are sources in the first case and binaries in the latter case. > So from your perspective, yes, they will appear "out of the blue". Out of the blue == outside anything specified by (rpm speak) sources and patches. There is usually no good reason to create packages that use files out of the blue. > It is against most software rules/guidelines for distributing packages > with a distribution (e.g. Fedora) but not against rpmbuild rules. The > rpmbuild program allows this fine. The rpm process is okay with this. > It is a philosophical issue and not a technical one. You can abuse any software, yes, also rpmbuild, so in that sense it's not a technical issue. > Of course doing it this way is fine. But it is not required. Among > other things bundling a binary blob in like that allows a .src.rpm > file to be produced that could rebuild the binary .rpm file. But > because the source is not really source the .src.rpm file is not > really useful. It could not be used to port the code from 32-bit to > 64-bit for example. Therefore IMNHO in this type of case it does not > really add anything over just having the files appear out of the blue. I totally disagree, sorry. -- -- Jos Vos <jos@xxxxxx> -- X/OS Experts in Open Systems BV | Phone: +31 20 6938364 -- Amsterdam, The Netherlands | Fax: +31 20 6948204 _______________________________________________ Rpm-list mailing list Rpm-list@xxxxxxxxxx https://www.redhat.com/mailman/listinfo/rpm-list
