To Require or not to Require?

Michael Schwendt mschwendt at
Fri Aug 12 13:25:42 UTC 2011

On Fri, 12 Aug 2011 14:30:46 +0200, Andreas Schwab <schwab at> wrote:

> > The separate "bar" package still is entirely irrelevant
> It kills your entire argument.
> Andreas.

It still doesn't.
libfoo update would need to come first. First come, first served. And
what packaging techniques to apply in the libfoo update has been the topic
of this thread:

| I have a package (keyutils) that produces three RPMs: keyutils
| (programs), keyutils-libs and keyutils-devel.
| ...
| So does the keyutils rpm need an explicit Requires on the keyutils-libs
| rpm in the specfile or is the implicit library dependency sufficient?

Whether any other update built against libfoo would also benefit from
an explicit dep is covered by the guidelines:

More information about the devel mailing list