Re: [@core] working definition for the minimal package set

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



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. :)

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.

-- 
Matthew Miller  ☁☁☁  Fedora Cloud Architect  ☁☁☁  <mattdm@xxxxxxxxxxxxxxxxx>
-- 
devel mailing list
devel@xxxxxxxxxxxxxxxxxxxxxxx
https://admin.fedoraproject.org/mailman/listinfo/devel



[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
[Index of Archives]     [Fedora Announce]     [Fedora Kernel]     [Fedora Testing]     [Fedora Formulas]     [Fedora PHP Devel]     [Kernel Development]     [Fedora Legacy]     [Fedora Maintainers]     [Fedora Desktop]     [PAM]     [Red Hat Development]     [Gimp]     [Yosemite News]
  Powered by Linux