On Fri, Jan 16, 2009 at 12:43:03PM +0100, Michael Mraka wrote: > > And what about merging spacewalk and spacewalk-setup packages (whatever new > name will be)? If you configure a package via spacewalk-setup you definitely > need all that packge installed so it sould be required by spacewalk-setup > package. The rest of packages should be installed as dependencies of those > first level packages.
Well, we've used spacewalk as a "comps" package. Its primary task is to bring in the rest of needed packages to the rpm transaction. Yes, I've mentioned before that only top-level packages should be specified here, and the rest should be pulled in via a transitive hull. But spacewalk-setup actually has some code it in, and IMO it should only require those packages that are needed for spacewalk-setup to operate. > % So sum up, I plan to do the following changes: > % > % satellite/admin/ => spacewalk/admin/ > % satellite/certs/ => spacewalk/certs-tools/ > % satellite/config/ => spacewalk/config/ > % satellite/install/Spacewalk-Setup/ => spacewalk/setup/ > > remove the rest of satellite/install/* > > % remove satellite/schema/ > % satellite/spacewalk.spec => spacewalk/package/spacewalk.spec > % satellite/Makefile => spacewalk/package/Makefile Done now. I'll wait with the satellite/install/ removal until I get new place (Devan?) to put this. > Couple of other things: > * gzipstream/ contains zlib-python interface so we should move > gzipstream/ => spec-tree/python/gzipstream/ Well, looking into the gzipstream/gzipstream-1.4.0.tar.gz, we seem to actually be an upstream for that. So the .tar.gz should not be there, the content should be unpacked (and tarred during make srpm). But it's not spec-tree material. There are comments in the code about getting the functionality to gzip. Python guys, what are the plans? > * projects/cobbler/ - no spec there. I can see cobbler-setup there but > there is another cobbler-setup in satellite/install/Spacewalk-Setup/bin/. > Should be projects/cobbler safely removed? Cobbler guys? > * projects/ssl-cert-check/ - what about moving > projects/ssl-cert-check/ => spacewalk/ssl-cert-check/ > where people expects spacewalk-* packages? Hmm, we've actually did not ship this with Spacewalk 0.4. And we have bugzilla https://bugzilla.redhat.com/show_bug.cgi?id=461270 for the package to be replaced by certwatch. So I'll leave it to Dave to remove this once the code migrates to certwatch. > % Please raise your objections, > > And we should not forget to tag moved packages so rel-eng/packages/* point to > right location. I did that for the => spacewalk/ change. -- Jan Pazdziora Satellite Engineering, Red Hat _______________________________________________ Spacewalk-devel mailing list [email protected] https://www.redhat.com/mailman/listinfo/spacewalk-devel
