Right, sorry.
Ok, maybe some other ideas (totally untested):
1) You could then trim Base and Core down to the minimum that you want,
and then maybe add 2 other groups (i.e. Base2, Core2) that include the
packages that were taken out of Base and Core. Again, you would have to
explicitly include these for the regular installs; not sure if that is
possible for you.
2) You could hack anaconda. You could change instdata.py so that it
doesn't use Base and Core by default.
3) I am not sure if this is possible, but you may be able to copy the
comps.xml file that you want in the %pre section. It looks like the code
searches for the comps.xml file in this order: /tmp/updates/
'basetree'/RHupdates/ 'basetree'/RedHat/base/ . So, you could copy the
comps.xml file that you want to /tmp/updates/. I am not sure if this
will work at all...just pulling ideas out of my ...
Looking through the code quickly, I did not see a way to specify a
comps.xml file to use though...it looks like the name is hard coded.
--brett
On Tue, 2003-02-11 at 04:12, Smith, Eric V. wrote:
> But your number 1 can't apply to base and core, correct? At least
> that's my understanding and experience. You can add things to base and
> core, but you can't remove from them. I'm looking to not install
> packages like setserial and raidtools (and many others), which I'll
> never need for the boxes I'm configuring.
>
> And your number 2 can only add to base and core, where I'm looking to
> remove stuff from base and core.
>
> I realize I could remove packages after I've done the install, but I'm
> trying to minimize the size of the disks I need for these boxes. I'd
> rather just not install the stuff I don't need.
>
> Thanks for the ideas.
>
> > -----Original Message-----
> > From: Brett Schwarz [mailto:brett_schwarz@xxxxxxxxx]
> > Sent: Monday, February 10, 2003 11:27 PM
> > To: kickstart-list@xxxxxxxxxx
> > Subject: Re: Alternate comps.xml file?
> >
> >
> > I am not sure about specifying another comps.xml file, but there are
> > possibly 2 other solutions you may want to try:
> >
> > 1) If you are using kickstart (I assume because this is the kickstart
> > list), then explicitly list the packages that you want
> > installed for one
> > of the cases (presumably your "edited" case). And then don't edit
> > comps.xml. If you explicit list the packages, then it will never use
> > comps.xml. comps.xml will then only be used if doing a "regular"
> > install.
> >
> > 2) you could define your own groups within the comps.xml, and
> > leave the
> > other groups untouched. Then in your custom install, specify those
> > groups in the package section. During regular installs, it
> > would just be
> > normal.
> >
> > I think this should be possible, but I have never tried it...
> >
> > --brett
> >
> > On Mon, 2003-02-10 at 18:37, Smith, Eric V. wrote:
> > > Is it possible to specify an alternate comps.xml file? I
> > have editted
> > > comps.xml to remove packages from base and core, but I
> > still sometimes
> > > want to use the distributed comps.xml. Any ideas?
> > >
> > > Thanks.
> > >
> > >
> > >
> > > _______________________________________________
> > > Kickstart-list mailing list
> > > Kickstart-list@xxxxxxxxxx
> > > https://listman.redhat.com/mailman/listinfo/kickstart-list
> > --
> > Brett Schwarz
> > brett_schwarz AT yahoo.com
> >
> >
> >
> > _______________________________________________
> > Kickstart-list mailing list
> > Kickstart-list@xxxxxxxxxx
> > https://listman.redhat.com/mailman/listinfo/kickstart-list
> >
>
>
>
> _______________________________________________
> Kickstart-list mailing list
> Kickstart-list@xxxxxxxxxx
> https://listman.redhat.com/mailman/listinfo/kickstart-list
--
Brett Schwarz
brett_schwarz AT yahoo.com
