Yes that's true but I was hoping to only have to maintain one .spec file and such. Ah well, maybe the KISS approach is best in this case. Also, is there a way I can define a "function" in my spec file? Aaron On 6/25/07, Jos Vos <jos@xxxxxx> wrote:
On Mon, Jun 25, 2007 at 06:33:01PM +0200, Aaron Lippold wrote: > I am registering a set of files in a db. Some users only need the > first set of files, some need all the files from each set in the db. I > want to allow the option to say, 'I need set1 and set3' etc. etc. > > MyFiles/Set1/file1.1,file1.2,file1.3,... > .../Set2/file2.1,2.2,2.3,... > ../Set3/file3.1,3.2,3.3,... > > If they user only wants to install the files in Set1 I want to have an > option/switch they can pass to say, > > rpm -ihv --install-set1 --install-set3 my.rpm You could split the RPM into subpackages, each containing one "set". -- -- 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
_______________________________________________ Rpm-list mailing list Rpm-list@xxxxxxxxxx https://www.redhat.com/mailman/listinfo/rpm-list
