Re: Explicit "Requires" should (usually) be arch-specific

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

 



On Tue, 2009-09-15 at 19:12 -0400, Tom Lane wrote: 
> Braden McDaniel <braden@xxxxxxxxxxxxx> writes:
> > Since apparently a requirement for "foo" can be satisfied by any
> > available architecture for which a "foo" is available, "Requires" that
> > do not specify the architecture are unsafe for multilib systems (unless
> > the dependency really can be satisfied by any architecture--which does
> > not strike me as the most common case).
> 
> Surely this is a bug, not something that every single specfile must
> work around.

If it's a bug, then how do you propose a specfile should articulate a
"Requires" that *can* be satisfied by any architecture?

Or maybe I'm misunderstanding what you think the bug is...?

-- 
Braden McDaniel <braden@xxxxxxxxxxxxx>

--
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