[@core] working definition for the minimal package set

[Seth Vidal]

On Mon, 12 Nov 2012, Benny Amorsen wrote:

> Seth Vidal <skvidal at fedoraproject.org> writes:
>
>> fantastic. show me a deployment somewhere of a 'thin client' that
>> doesn't use their own custom kickstart/pxe for instantiating the
>> clients and that will be relevant to this discussion.
>
> Is kickstart installs generally out of scope for minimal package set?
> The problem used to be that even with kickstart, you ended up with a
> too-large package set which you then had to rpm -e at the end. Awkward.
>
> This has gotten much better, of course.
>
> Personally I was hoping that the minimal project would end up making it
> possible, using kickstart, to install enough to get yum running. Ideally
> the size of that minimal install would be rather small. The users can
> always add more... If people want an actual functional system out of the
> box, it seems that they would be better off with one of the other
> installation choices.
>
> But anyway, if it is possible to prevent the installation of openssh-*
> in the kickstart file, that is ok with me. rpm -e afterwards, not so
> much.
>


why is rpm -e in %post in the kickstart not okay?

the system isn't 'up'. what harm is it in cleaning up crap? If you're 
doing enough installs that the bandwidth is an issue in installing these 
additional packages then you should make a local mirror, I'd think.

-sv