On 11/12/2012 05:25 PM, Matthew Miller wrote:
On Mon, Nov 12, 2012 at 12:27:34PM -0800, Jesse Keating wrote:
But there was a non-UI way. Does that no longer work?
The non-UI way was kickstart. But you can't deselect (-) mandatory
packages in a group. @core is primarily made up of mandatory
packages.
Huh. I could swear I've done that before and it worked. In any case, it is
_certainly_ working with appliance-creator right now. :)
>
appliance-creator may not force @core. The force of @core is an
anaconda thing.
This actually opens up another axis, here, so we could have one standard for
mandatory packages (kernel+init, or up-to-yum+net) and a second level for
default (up-to-yum+net, +ssh,cron,etc). Even without a UI exposed, the
distinction between mandatory and deselectable is huge for kickstart, which
I think is common for _most_ of our use cases.
Yeah, that's a thing that probably could be done. Bug again I'd like
some input from people who have made the switch to these packages being
mandatory.
--
Help me fight child abuse: http://tinyurl.com/jlkcourage
- jlk
--
devel mailing list
devel@xxxxxxxxxxxxxxxxxxxxxxx
https://admin.fedoraproject.org/mailman/listinfo/devel
