On Fri, Aug 03, 2012 at 10:49:44AM -0700, Jesse Keating wrote: > 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.
That's not how pungi is currently working, a "minus-package" seems to unconditionally exclude the package. I don't see what the --exclude statement would do in %packages in a kickstart file. It is also not listed in the anaconda documentation: http://fedoraproject.org/wiki/Anaconda/Kickstart#Chapter_3._Package_Selection However, the "minus-package" statement is (for anaconda) described as "You can also specify which packages not to install from the default package list" which is certainly not how pungi is handling it now. I think I'll file a bug and see what the pungi maintainers think. -- -- Jos Vos <[email protected]> -- X/OS Experts in Open Systems BV | Phone: +31 20 6938364 -- Amsterdam, The Netherlands | Fax: +31 20 6948204 -- buildsys mailing list [email protected] https://admin.fedoraproject.org/mailman/listinfo/buildsys
