Hello everyone,
I'm working on building a yum repo generator from Spacewalk sources.
It will function like this:
Jump into the Spacewalk API, snag all the packages. Build them into a list.
Insert all the data into a sqlite database (easiest way to power this
type of project I think, no I don't want to hook into the life DB
either, it should be DB free imo).
Download metadata for each package, insert into the sqlite database.
Build various files {other,primary,filelists}.xml
Now here's my question. Before I get to involved in something that may
or may not work, from my understanding <location href="something.rpm">
can point to a full URL correct? As in
"http://spacewalk/bla/bla/bla/something.rpm";?
If not, the only other solution I can think of is writing an apache
mod_rewrite rule for each package. This repo is ideally going to sit
on the Spacewalk server, so doing some rewrites isn't that big of a
deal. Considering the goal is to simply create yum repos from
Satellite packages and channels I think these are logically my best
two options without entering the database.
My reasons for not entering the database are the following:
1. Security policies in the office.
2. My Oracle-fu sucks.
So if someone says that I should be pulling the DB directly and can
give me a few good reasons, and possibly be willing to let me bounce
some queries off them, I would be more than happy to do it that way.
It would be quicker after all.
--
Steven Crothers
steven.croth...@gmail.com
_______________________________________________
Spacewalk-devel mailing list
Spacewalk-devel@redhat.com
https://www.redhat.com/mailman/listinfo/spacewalk-devel
