[Fedora-packaging] [Guidelines Change] Changes to the Packaging Guidelines
Mamoru Tasaka
mtasaka at ioa.s.u-tokyo.ac.jp
Fri Feb 4 19:24:33 UTC 2011
Tom Callaway wrote, at 02/05/2011 02:18 AM +9:00:
>
> In some situations, this is not a problem, but there are some situations
> where it does matter:
>
> * A library that is explicitly Required (example a dlopen'd library)
> * The dependency from one -devel packages that is not noarch to
> another -devel package.
> * A non-noarch subpackage's dependency on its main package or another
> subpackage (e.g., libfoo-devel depends on libfoo, or fooapp-plugins
> depends on foo-app).
>
> The Packaging Guidelines (and Naming Guidelines) have been amended to
> reflect that %{?_isa} must be used for Explicit Requires and Provides
> that match those situations.
>
> http://fedoraproject.org/wiki/Packaging:Guidelines#Requires
> http://fedoraproject.org/wiki/Packaging:Guidelines#Explicit_Requires
> http://fedoraproject.org/wiki/Packaging:Guidelines#Requiring_Base_Package
> https://fedoraproject.org/wiki/Packaging:NamingGuidelines#Renaming.2Freplacing_existing_packages
>
So
- 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?
Regards,
Mamoru
More information about the packaging
mailing list