----- Original Message ----- > Thanks all for the replies. The reason to use RPM is to be able to download > self made configuration/repo files from my Spacewalk server. The RPM will > have all the necessary files to configure the local system to be attached to > spacewalk. This just will make it simple for my enduers not having to edit > repo files not copy the RPM from their local workstation to the new system > their built. Using RPM with the HTTP functionally just makes it easier to > attach. And from that point Spacewalk will take care of the rest.
You could drop the RPM into /var/www/html/pub on your spacewalk-server and your users could then get it from http://<spacewalk-server-fqdn>/pub/file.rpm Does that cover your usecase? G > > Thanks again! > > Glen Collins > > > > > Yes, hence my remark that you could use rpm and URLs with this setup if you > want. Was just giving a working example. > > > > > On 2014-09-16 10:10, Thomas Foster wrote: > > > > Its the same..createrepo creates the necessary files to allow yum to download > the files from a webserver. > _______________________________________________ > Spacewalk-list mailing list > [email protected] > https://www.redhat.com/mailman/listinfo/spacewalk-list > > > _______________________________________________ > Spacewalk-list mailing list > [email protected] > https://www.redhat.com/mailman/listinfo/spacewalk-list _______________________________________________ Spacewalk-list mailing list [email protected] https://www.redhat.com/mailman/listinfo/spacewalk-list
