-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 First off, I've read through the list archives, and there are so many conflicting methods for doing this, I'm back to square one. In redhat, all I would do is symlink my packages into my main RPM directory, then run genhdlist. My understanding from Novell's very spares documentation is that I would do something similar, but it does not work, and breaks in a rather ugly way each time. My source tree looks like this : rwxr-xr-x 6 root root 456 Nov 3 17:17 . drwxr-xr-x 5 root root 152 Nov 3 16:20 .. drwxr-xr-x 7 root root 168 Nov 3 10:17 SUSE-CORE-Version-9 drwxr-xr-x 5 root root 120 Nov 3 10:42 SUSE-SLES-9-Service-Pack- Version-2 drwxr-xr-x 3 root root 72 Nov 3 10:11 SUSE-SLES-Version-9 lrwxrwxrwx 1 root root 28 Nov 3 10:58 boot -> SUSE-SLES- Version-9/CD1/boot lrwxrwxrwx 1 root root 31 Nov 3 10:58 content -> SUSE-SLES- Version-9/CD1/content lrwxrwxrwx 1 root root 35 Nov 3 11:07 control.xml -> SUSE-SLES- Version-9/CD1/control.xml lrwxrwxrwx 1 root root 51 Nov 3 11:07 driverupdate -> SUSE- SLES-9-Service-Pack-Version-2/CD1/driverupdate lrwxrwxrwx 1 root root 44 Nov 3 10:58 linux -> SUSE-SLES-9- Service-Pack-Version-2/CD1/linux lrwxrwxrwx 1 root root 31 Nov 3 11:02 media.1 -> SUSE-SLES- Version-9/CD1/media.1 - -rw-r--r-- 1 root root 5081 Nov 3 16:41 part.xml drwxr-xr-x 2 root root 104 Nov 3 10:18 yast I've tried adding packages to: SUSE-CORE-Version-9/CD1/suse/x86_64 SUSE-CORE-Version-9/CD1/suse/addons SUSE-CORE-Version-9/CD1/suse/updates SUSE-SLES-9-Service-Pack-Version-2/CD1/suse/x86_64 SUSE-SLES-9-Service-Pack-Version-2/CD1/suse/addons SUSE-SLES-9-Service-Pack-Version-2/CD1/suse/updates SUSE-SLES-Version-9/CD1/suse/x86_64 SUSE-SLES-Version-9/CD1/suse/addons SUSE-SLES-Version-9/CD1/suse/updates From the "suse" directory all of those above paths, I've tried: create_package_descr -x ./setup/descr/EXTRA_PROV -d . create_package_descr -x ./setup/descr/EXTRA_PROV -d addons create_package_descr -x ./setup/descr/EXTRA_PROV -d updates The effect is the same, either errors during the autoyast, which is unable to find the added rpms, or a newly created depdency hell where autoyast tries installing conflicting versions of packages like lvm, and becomes unusable (only fixable by rebuilding my source-tree). Does anybody have a good answer to a working way, that doesn't involve "please look back through the archives"? I'd be really grateful! -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.1 (Darwin) iD8DBQFDaxHZwjCqooJyNAMRAsw2AJ9BkXwIpNdKEKY3KrDJRrlNMZ009QCeOv3T Ma10UO+eSKx1032vvTvEXwA= =nl2K -----END PGP SIGNATURE-----