On Sun, Jul 04, 2010 at 12:06:39PM +0200, Michael Schwendt wrote: > And there would be drawbacks, too, for a hardcoded "Req => BR" rule. > It would make circular deps impossible: Pkg A requires Pkg A-extras, > and Pkg A-extras BR Pkg A. It would make bootstrapping a dist more > complicated. For this example Pkg A-extras already BRs itself, how will the Req => BR rule make it worse? > For some pkgs (e.g. leaf pkgs) it is fine if they are > not available in the buildroot when building a pkg that requires the > leaf pkg at run-time. If a package is required at run-time, it is not a leaf package, because a leaf package is a package that is not required by something else. > For other pkgs it is fine if you build them > with an old build tool for a target env that is build upon a newer tool. But this has nothing to do with ensuring the run-time deps are available at build time. Off course then the BRs are not really required then, but this is what all this is about. But in case this rule makes it impossible to build certain packages, than there obviously needs to be a way to disable this rule, but it can still be default if it usually is considered to be a benefit. Regards Till
Attachment:
pgpVQQS15ywLR.pgp
Description: PGP signature
-- devel mailing list devel@xxxxxxxxxxxxxxxxxxxxxxx https://admin.fedoraproject.org/mailman/listinfo/devel
