Todd,
we do this - I have yum based repository backends to manage our add-on
software, but I wanted to give the installation sources yet another try
after the disasters with SLES8 and SLES9 but it looks like @ novell nobody
learned something and they're still using the same ugly mechanisms....
(sometimes I have the impression that this system is maybe a legacy from
pre-novell times and the people that worked on it are no more in the
company)
In my opinion it's not the intention of the installation system to build a
second repository infrastructure (beside the yast / installation source
system) for additional packages. This makes no sense and does not reduce
administrative work.
At the moment we're starting the installation with the yast2 installation
sources and we're finishing the package installation with yum repositories
which costs a lot of disk space (ok symlinks can help there) and is really
bad to administrate.
Sometimes I got the impression, that maybe I missed something in the
documentation - but no ... there must be magic in building a installation
source like they're on the CD ...
Also I wanted to avoid a lot of my postinstall scripts (which in the latest
SLES9 were about 14 scripts) and try using that what Novell provides to us.
I think Novell / SuSE should have a look at this issue and maybe in code 11
bring out something better and more consistent than the installation source
system. With the ZEN framework, they're now supporting a lot of other
repository types - so please get rid of the installation source system, or
do something that makes it better to handle, more easy to understand, more
easy to administrate and more easy to customize. (maybe have a deeper look
at yum or apt-get to adopt their repository techniques).
Regards
marco
P.S.: Still, I am really interested in a script which builds a plain
installation source structure that I can just put in my RPM's and point to
it during installation.
"Ness, Todd"
When try to install a package a message like this appears: http://yastserver/packages/repo2/updates/: Can't open /var/lib/zypp/cache/Source.08MaOg/DATA/descr/packages
I have never seen that message
And this is the repo2 tree:
if repo1 is your original SUSE installation source, then your "updates" addon directory must be in the repo1 directory. Not in a self created parallel repo2 directory. Does your installation source look like the tree in the FAQ? -- ciao, Uwe Gansert Uwe Gansert, Server Technologies Team SUSE LINUX Products GmbH, Maxfeldstrasse 5, D-90409 Nuernberg, Germany Business: http://www.suse.de/~ug now playing Faderhead - Vanish (Extended Version) -- To unsubscribe, e-mail: suse-autoinstall-unsubscribe@suse.com For additional commands, e-mail: suse-autoinstall-help@suse.com -- To unsubscribe, e-mail: suse-autoinstall-unsubscribe@suse.com For additional commands, e-mail: suse-autoinstall-help@suse.com