The non-rpm files will not pose a problem. I imported HPs repo a few says ago without problem.
I would wonder though why you don't have more o a 1:1 repo:channel relationship, and then manage membership using the same methodology as with channels. For example, I have custom channels for each third-part/ISV component that makes up part of our standard opener rating environment (SOE). You could then also have separate activation keys which enable a particular SOE +HP_Proliant, or +VMWare_guest. You could then put in some logic in the kick start which does some hardware inspection and uses a comma-separated list of activation keys. However, this is currently a hypothesis, and is not something I have actively explored. -- Cameron Kerr On 11/12/2012, at 3:09 AM, "Ciro Iriarte" <[email protected]<mailto:[email protected]>> wrote: Hi!, do you guys usually include repo from hardware vendors?, HP and Dell have their utilities in public repositories but HP includes some non RPM files in there also, can that be handled by spacewalk? Ref: http://downloads.linux.hp.com/SDR/downloads/SPP/suse/SLES11/x86_64/current/ Currently I have 4 channels with all the related repositories linked to them: sles11-x86_64-vmware sles11-x86_64 rhel5-x86_64 rhel6-x86_64 What would be the best way to organize them?, should I keep this organization adding Dell and HP to each channel or create different channels with repos for each vendor? Regards, -- Ciro Iriarte http://cyruspy.wordpress.com -- _______________________________________________ Spacewalk-list mailing list [email protected]<mailto:[email protected]> https://www.redhat.com/mailman/listinfo/spacewalk-list
_______________________________________________ Spacewalk-list mailing list [email protected] https://www.redhat.com/mailman/listinfo/spacewalk-list
