Miroslav Suchý wrote:
I suggest to split yum repo to two parts. One is Spacewalk and Proxy.
Second is client tools.
Do you agree? Do you disagree? Any comments?
OK. No objections heard.
Jesus can you give me contact on RH person responsible of
http://spacewalk.redhat.com/yum/ ?
If I understand the process I had to prepare the content in
svn/branches/spacewalk_web/
once done, send ticket to ????
And that is all.
Dennis, can you do the necessary steps (in mash?) to generate two yum repos?
Client packages should be:
rhcfg*
rhn-custom-info
osad
rhn-applet-actions
rhn-custom-info
rhn-kickstart*
rhn-virtualization*
spacewalk-koan
rhnlib
rhnmd
rhnsd
rhn-check
rhn-setup
yum-rhn-plugin
koan
spacewalk-certs-tools
spacewalk-koan
Everything else should stay in the yum repo as it is now.
From Brandon's list I rejected:
jabberpy
perl-IO-stringy
rhnpush
spacewalk-proxy-installer
spacewalk-ssl-cert-check
spacewalk-ssl-cert-check
They are needed for Spacewalk server/Proxy and with older releases it
may be unable to install or run. So we should have them server yum repo
and not in client repo.
--
Miroslav Suchy
Red Hat Satellite Engineering
_______________________________________________
Spacewalk-devel mailing list
[email protected]
https://www.redhat.com/mailman/listinfo/spacewalk-devel
