On 11/28/06, Jonas Karlsson <[EMAIL PROTECTED]> wrote: > On Tue, 28 Nov 2006 18:46:24 +0100, Hisham Muhammad > > Notice also that the structure of trunk/ mirrors that of LocalRecipes/ > > and revisions/ mirrors that of Recipes/. > > > Ok, that make somewhat sense. So for every version in trunk/ there's a > same version, but with a -r1 suffix, in revisions/?
Yes. I'm about to populate revisions/ right now, actually. > Then I'd like to make > some adjustments to some scripts, for example NewVersion. > See NewVersion row 79 and forward: > > mkdir -p "$destinationDir/$packagename" > cp -R "$oldrecipedir" "$newrecipedir" > > if Quiet svn info "$destinationDir" > then > Quiet svn add "$destinationDir/$packagename" > Quiet svn add "$destinationDir/$packagename/$newversion" > fi > > cd "$newrecipedir" || Die "Failed creating new recipe dir." > > To simplify svn handling. Scripts to simplify svn handling will certainly be done. But we have to think things over very well on how to handle this. We want to make its use the least bureaucratic as possible, while still retaining a good history of where changes in recipes come from (making good use of 'svn copy'). For instance, I think we'll need a script to get a recipe tarball sent by a user, svncopy the latest version of the program from the trunk and then apply the differences of the user's recipe over the copied version, so that the file in the server retains the full history across versions instead of looking like a fresh Recipe file. -- Hisham _______________________________________________ gobolinux-devel mailing list [email protected] http://lists.gobolinux.org/mailman/listinfo/gobolinux-devel
