On Tue, Nov 08, 2005 at 10:04:05AM +0100, Uwe Gansert wrote:
On Tuesday 08 November 2005 01:20, T. Ribbrock wrote:
Hm, I think I might have misinterpreted your second mail (the one explicitly stating not to cd into the SuSE-SLES9-CORE (or what it's called) directory.
Ha! Yesterday, on my way home, it came to my mind that that might has happened. The "SuSE-SLES9-CORE" directory on a SLES is really on that level that would be called "/PATH/TO/SuSE/SLES9/" in your structure. The structure of a SLES9, with all it's service packs, looks quite different than a normal 10.0 or 9.3
Yup, you're right - that was it. As soon as the "updates" directory ends up in "10.0" (i.e. the directory where all the media.[1-5] and directory.yast etc. are located in), all is well. BUT: Given that you poked me with the right keywords, I got adventurous and discovered that this whole issue is MUCH, MUCH EASIER to accomplish: Let's rehash: I wanted to add the Packman repository as a second repository for the autoinstall. This is a fully operable repository. And here is what you need to do to add it to the installation sources: 1) cd SOURCE_DIR N.B.: This is the directory containing media.*, boot, ARCHIVES.gz and all that - in my case "10.0" 2) Copy the complete, working repository as a new directory into SOURCE_DIR. This has to be the directory that you can also give to YaST2 as an installation source. In my case I had to copy the Packman/suse/10.0 directory and it ended up being SOURCE_DIR/Packman 3) Make a new directory called "yast" in SOURCE_DIR if it doesn't already exist 4) cd yast You need to have two files in there: instorder and order Modify/create them to contain all necessary pointers to the original SOURCE_DIR (denoted as '/') and the new repository directory. In my case, 'instorder' looks like this: /Packman / and 'order' looks like this: /Packman /Packman / THAT'S IT! If you now add packages from this repository to your package list in autoinst.xml, they will get installed. In fact, the additional repository will show up with a full name and as a CD in the install screen when autoyast is installing the system. And YES, you CAN add more than one extra repository that way (I'm using two at the moment). CAVEAT EMPTOR: As I discovered, using this feature has potential downsides: In my case, I'm using Packman and among other things, they have packages that are simply a newer version of an existing SuSE package. If you choose to install that package, YaST2 will pick the newer one, which means you could end up with more "non-standard" packages than you bargained for. I'm currently having the problem that I do want the Packman version of xmms (for MP3 support) but not the Packman version of xsane/sane (I have no reason to). Usually, I prefer to keep as much standard as possible, as that prevents some update headaches e.g. for security fixes. Personally, I have yet to decide what to do about this - I could modify the Packman repository to remove all packages I don't want (obviously, I need create_package_descr again in that case), but that means that mirroring the repo gets a bit more complex. Or I could revert to my original method, which are init scripts with an "installation_source" command and a few "y2pmsh isc PACKAGE" commands. That solution requires more effort when making/testing those commands. <sigh> Decisions, decisions... Anyway, thanks for pointing me in the right direction, Uwe! Cheerio, Thomas