On Jul 10, 08 10:53:08 -0500, Archie Cobbs wrote:
Regarding the benefit of doing supporting spec + _aggregate, here's the benefit I see:
1. You are building RPM A. 2. RPM A BuildRequires: B, C, D and Requires: B, C, D. 3. No other package in your project requires B, C, or D. 4. You have decided (for whatever reason (separate discussion*)) to aggregate B, C, and D
In this situation, it seems more logical to aggregate B, C, and D all at once, using an _aggregate file in package A (therefore better encapuslating the dependencies), rather than creating three new packages B, C, and D each with their own _aggregate file.
I believe the best practice for this is a subproject, in which you have A, B, C, D as seperate packages. This also gives you the desired encapuslation. cheers, Jw. -- o \ Juergen Weigert paint it green! __/ _=======.=======_ <V> | jw@suse.de (not a debating __/ _---|____________\/ \ | 0911 74053-508 excercise.) __/ (____/ /\ (/) | _____________________________/ _/ \_ vim:set sw=2 wm=8 SUSE LINUX Products GmbH, GF: Markus Rex, HRB 16746 (AG Nuernberg) --------------------------------------------------------------------- To unsubscribe, e-mail: opensuse-buildservice+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-buildservice+help@opensuse.org