On Tue, 2008-11-25 at 10:23 +0100, Jeroen van Meeuwen wrote:
pungi extends the yum exclude list, eliminating the packages from
the
package sack (src/pypungi/__init__.py:339), and those will thus not be
available during package selection, nor dependency resolving, nor
whatever other stage except buildinstall.
livecd-tools only removes the packages in the exclude list after the
complete groupLst and packageLst have been selected. Ergo, after
dependency resolving, "excluded" packages may have been pulled back in.
Thinking about it some...
Ok, I think it all depends on where the exclude is encountered. If an
exclude is encountered at a repo declaration line, that should be passed
into the yum object like pungi is doing. But if the exclude (or -foo)
is encountered in %packages, it should be treated differently, it should
be treated the same way they would be treated should the kickstart file
be used with anaconda to perform an install. That is the way that
livecd-tools is doing it, so that things with - signs could still get
pulled in if they are needed to resolve deps of other things selected.
Obviously I have a bug in pungi with this, I'll be looking into it.
--
Jesse Keating
Fedora -- Freedom² is a feature!
identi.ca:
http://identi.ca/jkeating