Re: [suse-autoinstall] Custom package installation using AutoYaST
I am using SUSE SLES version 9. My requirement is
to put all my packages in a separate directory and to
install it. My control file is given below.
<software>
<addons config:type="list">
<addon>Base-System</addon>
<addon>X11</addon>
<addon>YaST2</addon>
</addons>
<base>Minimal+X11</base>
On Tuesday 26 April 2005 16:28, boopathy krishnamoorthy wrote:
I had customised the installation using
AutoYaST.
For adding my own package to install using AutoYaST, i had created a directory "custom" under "install_root/suse/". # ls suse i586 custom noarch nosrc setup src x86_64
In the control.xml i added the following portion
</software> custom <packages config:type="list"> <package>glibc</package> <package>libnscd</package> </packages>AFAIK since version 9.1 it's not necessary to enhance the autoast profile. Just do: cd INSTALLATION_ROOT/suse cp my.rpm ./i586/ create_package_descr -d . -x setup/descr/EXTRA_PROV
at the next installation, the new RPM should be found
-- ciao, Uwe Gansert
Uwe Gansert, Server Technologies Team SUSE LINUX Products GmbH, Maxfeldstrasse 5, D-90409 Nürnberg, Germany e-mail: uwe.gansert@suse.de, Tel: +49-(0)911-74053-0, Fax: +49-(0)911-74053-476, Web: http://www.suse.de
-- To unsubscribe, e-mail: suse-autoinstall-unsubscribe@suse.com For additional commands, e-mail: suse-autoinstall-help@suse.com
________________________________________________________________________ Yahoo! India Matrimony: Find your life partner online Go to: http://yahoo.shaadi.com/india-matrimony
On Thursday 28 April 2005 12:55, boopathy krishnamoorthy wrote:
I am using SUSE SLES version 9.
my suggestion should work on SLES9 too.
My requirement is to put all my packages in a separate directory and to install it.
why do they have to be in a seperate directory? If the packages are updates for existing packages, create the update directory on the installation source (I can explain it again but it is in the archive of this list too). If they are new packages which are new to the installation source, copy them to all the other packages an rebuild the package database like I explained.
custom <packages config:type="list"> <package>glibc</package> // this is my <package>libnscd</package> // package list </packages>
where is this way of adding own packages to an installation source documented?
I didn't use and selection file. I had given it directly in the control file itself.
if you go my way, it will look like this: <software> <addons config:type="list"> <addon>Min</addon> </addons> <base>Minimal</base> <packages config:type="list"> <package>MyOwnPackage</package> </packages> </software> no need for creating a selection file too. -- ciao, Uwe Gansert Uwe Gansert, Server Technologies Team SUSE LINUX Products GmbH, Maxfeldstrasse 5, D-90409 Nürnberg, 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 (2)
-
boopathy krishnamoorthy
-
Uwe Gansert