Re: Re: -devel arch dependencies

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



On Thursday 12 April 2007 15:09:47 Matthias Saou wrote:
> I did the latter, but IIRC it is preventing me from installing some
> apps that are only available in 64bit and require the gecko engine
> which still hasn't been split out.

And it won't either.  Mozilla decided that they don't want gecko to be a 
platform.

> Anyway, in the end my vote would be to change yum's behaviour from
> "install all available archs of the latest version" to "install best
> available arch of the latest version" when no arch is specified, and
> not have anaconda install any compat 32bit packages by default.
>
> As a side note, this is something I have always found quite annoying
> too : Any explicit package requirement from within a package also
> "triggers" the installation of all available archs (which is actually
> coherent with the current behavior, but annoying nevertheless).
> Example : If your package explicitly "Requires: curl" although it only
> really requires libcurl.so.3, which rpm also added automatically,
> you'll end up with curl.i386 and dragging in all of its dependencies.
> Without the explicit requirement, only curl.x86_64 would have been
> necessary.

Those are packaging bugs regardless of how yum / rpm handle them.  Explicit 
Requires should be avoided if the rpm will pick up library requirements on 
its own.

-- 
Jesse Keating
Release Engineer: Fedora

Attachment: pgp9i6PYgUogX.pgp
Description: PGP signature

--
Fedora-packaging mailing list
Fedora-packaging@xxxxxxxxxx
https://www.redhat.com/mailman/listinfo/fedora-packaging

[Index of Archives]     [Fedora Users]     [Fedora Desktop]     [Fedora SELinux]     [Big List of Linux Books]     [Yosemite Forum]     [KDE Users]

  Powered by Linux