createrepo future
seth vidal <[email protected]>
| Newsgroups | gmane.linux.rpm.metadata |
|---|---|
| Message-ID | <1186599106.712.40.camel@cutter> |
Hi folks, I've been pretty silent about createrepo for a while now. Mostly been busy with other things but some items have been going on in the background. There are a lot of things that need to change to make createrepo more useful to various programs out there.(buildsystems, dynamic-web-repos, things like puppet, etc) So, with that in mind I've made some changes to where we should go from here: 1. switch from cvs to git for scm. I'm not 100% excited about git but it's easy enough to setup for the shared repo storage and I'm getting more used to it for yum. All the info about accessing the repo via git is here: http://linux.duke.edu/createrepo/ 2. I've made a 'maintenance' branch of createrepo in that git repository. That's where all the work for 0.4.X's will go, so we can apply patches to the existing code base while working on a new one. (git checkout -f maintenance) 3. the new code base. Nothing is written up all that well, but we do have a need for a createrepo that's more usable as a module than as a executable program. Specifically, we need module code to return the metadata from any given package so it can then be crammed into a db or any number of arbitrary formats. It would also be nice to do work on the other side of the repodata. So we could easily take 2 repositories and produce differences, unions or intersections of them. There's a lot of work and not a lot of specification for this but it does need to happen. I figure the only way it will happen is with an almost ground-up rewrite, actually. so that is what the 'master' branch on git is for. So, that's where we are. Thanks, -sv