Pungi and anaconda interpret %packages differently
On 08/03/2012 03:03 AM, Jos Vos wrote:
I found out that pungi interprets %packages listed with a minus sign
(e.g. "-packagename") different from anaconda. Is this "by design"?
To be more precise:
When I specify a package in the kickstart file this way but other
packages in the list depend on it, the package is still installed
by anaconda (which is ok, I think). But pungi will always exclude
the package from the generated media, regardless the fact that
other packages depend on it.
It is not a big problem, I can just leave out all the minus-entries
in the pungi %packages list (it's not that much extra space), but a
consistent behavior would be nicer.
Any comments on this?
Another way that pungi differs is that it will do inclusive dep
resolution (grabs /every/ solver of a dep) vs an anaconda install which
will only grab the best solver of a dep.
That said, I think when I originally coded pungi, I wanted - to work
just like how anaconda does it. Don't include it, but allow it to be
brought in via deps. Because %packages can have --exclude statements it
is easy to fully exclude something from being brought in.
If that's not how pungi is currently working, sounds like either a bug
or a feature change after I stopped maintaining it.
Help me fight child abuse: http://tinyurl.com/jlkcourage
buildsys mailing list