RE: [suse-autoinstall] package selection question
-----Original Message----- From: Stefan Voss [mailto:stefan.voss@itellium.com] Sent: Thursday, September 29, 2005 11:21 AM To: suse-autoinstall@suse.com Subject: Re: [suse-autoinstall] package selection question
Am Donnerstag, den 29.09.2005, 17:11 +0200 schrieb Joe Landman:
Is it possible to list all the packages we want in the install rather than use one of the pre-selected package groups? I will check for dependencies, but I want to trim down the install we are doing (on a linux cluster node). Thanks.
Like this?
<software> <base>Minimal+X11</base> <packages config:type="list"> <package>bindutil</package> <package>bonnie</package> ... </packages> </software>
I think the question is whether it's possible to skip the <base>Minimal</base> part, and explicitly state every package that you want installed. Short answer, I don't think so...and you're just going to end up with the entire Minimal set anyway. There might be a couple of packages that aren't necessary, but almost everything in that set is necessary if you're going to end up with a bootable install.
I basically want to define something as minimal on my own, without a pre-defined selection. I can always install minimal and remove packages, but this rather defeats what I am trying to do. Joe Marlier, Ian wrote:
-----Original Message----- From: Stefan Voss [mailto:stefan.voss@itellium.com] Sent: Thursday, September 29, 2005 11:21 AM To: suse-autoinstall@suse.com Subject: Re: [suse-autoinstall] package selection question
Am Donnerstag, den 29.09.2005, 17:11 +0200 schrieb Joe Landman:
Is it possible to list all the packages we want in the install rather than use one of the pre-selected package groups? I will check for dependencies, but I want to trim down the install we are doing (on a linux cluster node). Thanks. Like this?
<software> <base>Minimal+X11</base> <packages config:type="list"> <package>bindutil</package> <package>bonnie</package> ... </packages> </software>
I think the question is whether it's possible to skip the <base>Minimal</base> part, and explicitly state every package that you want installed.
Short answer, I don't think so...and you're just going to end up with the entire Minimal set anyway. There might be a couple of packages that aren't necessary, but almost everything in that set is necessary if you're going to end up with a bootable install.
-- Joseph Landman, Ph.D Founder and CEO Scalable Informatics LLC, email: landman@scalableinformatics.com web : http://www.scalableinformatics.com phone: +1 734 786 8423 fax : +1 734 786 8452 cell : +1 734 612 4615
On Thursday 29 September 2005 17:26, Joe Landman wrote:
I basically want to define something as minimal on my own,
then don't hesitate to do that. The selections can be found in suse/setup/descr/ on your installation source. A small example for 10.0: =Ver: 4.0 =Sel: MyMinSel 10.0 65 noarch =Sum: MyMinSel =Cat: baseconf =Vis: true =Ord: 00 +Ins: ... packA packC ... -Ins Add your selection to the selections file then and fix the md5sum of "selections" in the MD5SUMS file. Add your selection to the MD5SUMS file too. In the autoyast profile do: <software> <base>MyMinSel</base> </software> keep in mind that the installation of dependent packages is still triggered. So if package A in your selection requires package B but B is missing in your selection, B will be installed anyway. So it might be that you'll end up with the minimal selection again (like Marlier Ian already pointed out) -- ciao, Uwe Gansert Uwe Gansert, Server Technologies Team SUSE LINUX Products GmbH, Maxfeldstrasse 5, D-90409 Nuernberg, Germany e-mail: uwe.gansert@suse.de, Tel: +49-(0)911-74053-0, Fax: +49-(0)911-74053-476, Web: http://www.suse.de
participants (3)
-
Joe Landman -
Marlier, Ian -
Uwe Gansert