Note: if you thought this was going to be a rant about keeping info files in CVS, sorry to disappoint you.
I have been keeping .info files for my packages in my own SVN repository for some time now, and IMHO things are working pretty well. The one thing that I think could use a little improvement is tracking when versions have been pushed from my local directory to unstable, and from unstable to stable (or when another maintainer commits a change to CVS, and I blindly overwrite that with local changes when upstream releases a new version). Has anyone set up something like this, where you can easily summarize what packages need to be tested, then promoted? (I know there is something like this on the PDB for all packages, but I figure this could most easily be tracked locally, especially since the PDB has no concept of my local/ directory, and takes some time to update.) I know just enough about Git to be dangerous, so if you have more git-fu please shoot holes in this idea: stable, unstable and local are all Git repositories (with appropriate ignore rules for both CVS metadata and packages which I don't maintain). The unstable repository is cloned from local, and both are seeded with the unstable tree from CVS (similarly, stable is cloned from unstable, but with the actual contents imported from CVS). A typical package update might involve the following steps: 1) fink selfupdate-cvs 2) cd unstable; git commit -a 3) merge unstable -> local 4) hack in local; commit 5) merge local -> unstable Thoughts? Should I be using Git branches for stable/unstable/local? Would this sort of merge be reasonable for SVN 1.5+? -- - Charles Lepple ------------------------------------------------------------------------------ _______________________________________________ Fink-devel mailing list [email protected] http://news.gmane.org/gmane.os.apple.fink.devel
