Hi, I've started a new script that recipe maintainers will use to interface with the recipe store in CVS. I committed an initial revision to CVS (latest Scripts and Compile required) so you all could take a look and I could get some feedback.
For safe testing, I'm using a local CVS repository. You can try it like this: ~] cd /Depot /Depot] mkdir LocalCVSRepo /Depot] cvs -d:local:/Depot/LocalCVSRepo init /Depot] mkdir LocalCVSRepo/RecipeBook /Depot] cd ~ ~] cvs -d:local:/Depot/LocalCVSRepo co RecipeBook ~] cd RecipeBook now you should be able to copy unpacked recipes (you know, the Foo/1.0/Recipe trees) inside RecipeBook and call PackRecipe --tag. Example: ~/RecipeBook] cp -a /Files/Compile/LocalRecipes/Foo . ~/RecipeBook] PackRecipe --tag Foo/1.0 CVS interaction only happens if you use --tag. If you don't, it will pack a recipe using "rLOCAL" as the revision code. Once you pack a revision, fiddle around with the recipe and run PackRecipe --tag Foo/1.0 again. The idea is that one should be able to work freely in the recipe and then commit changes to CVS with a PackRecipe --tag. It should not be necessary to use 'cvs' commands by hand to make changes to a recipe. PackRecipe should never leave the local CVS repository in an "inconsistent" state (with uncommitted changes). But in case it aborts halfway through for whatever reason and that happens, there's a --cleanup flag that should "refresh" the state of the recipe (it will not rollback changes in files; it will just reload its CVS control directories). Try ~/RecipeBook] PackRecipe --cleanup Foo/1.0 and then try again to see if things turn back to normal (you can run --tree --cleanup at once, as well). Give it a spin and let me know who well/badly it performs. Feedback is welcome. Thanks, -- Hisham _______________________________________________ gobolinux-devel mailing list gobolinux-devel@lists.gobolinux.org http://lists.gobolinux.org/mailman/listinfo/gobolinux-devel
