On 02/04/2011 02:24 PM, Mamoru Tasaka wrote: > - Does this mean that mass packaging change will occur? > - Currently rpmbuild detects pkgconfig .pc dependencies, so for -devel > packages containing pkgconfig .pc file now we usually don't have write > dependency for another -devel subpackage like "Requires: foo-devel" > explicitly (as rpmbuild automatically adds "Requires: pkgconfig(foo)") > (and I guess we shouldn't write such explicit requires when possible > and let rpmbuild handle such dependencies automatically) > > If dependencies between (non-arch) -devel packages must be changed to > explicit arch-specific, it means that rpmbuild should also be changed > to add arch-specific pkgconfig Provides / Requires (e.g. > pkgconfig(x11)(x86-64) instead of current pkgconfig(x11)) ? > > - And as far as I am correct this also applies to other virtual Provdes/Requires > rpmbuild will automatically add. > - For example perl(BDB) devendency on perl-Coro.x86_64 will be satisfied by > perl-BDB.i686? Then this type of all virtual provides / requires rpmbuild > will handle must be changed?? > > Unless I am wrong to make things consistent such changes on rpmbuild must > be required. However is this actually we want? The Guidelines currently only cover Explicit Requires and Provides, the examples you point out are all implicit (Virtual). That isn't to say that perhaps these items should also be arch specific, where applicable, just that they are not yet addressed in the guidelines. ~tom == Fedora Project -- packaging mailing list packaging@xxxxxxxxxxxxxxxxxxxxxxx https://admin.fedoraproject.org/mailman/listinfo/packaging
