<div class="gmail_quote">On Sun, Jan 31, 2010 at 7:17 PM, Matteo Bernardini <span dir="ltr"><<a href="mailto:matteo.bernardini@sns.it">matteo.bernardini@sns.it</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex;">
hi fellas,<br>
<br>
looking for a way to manage building from current with sbopkg and mantain a modified <a href="http://slackbuilds.org" target="_blank">slackbuilds.org</a> repository I tried to use it with git.<br>
I pulled yesterday's repo and started doing tags for the build scripts I modified for clean build on current and then I merged them all.<br>
This is the patch I use (made with git diff from the first commit) against <a href="http://slackbuilds.org" target="_blank">slackbuilds.org</a> 13.0 repo<br>
<br>
<a href="http://ponce.pastebin.com/f70344f2a" target="_blank">http://ponce.pastebin.com/f70344f2a</a><br>
<br>
and this is the git repo itself<br>
<br>
<a href="http://github.com/Ponce/SBogit" target="_blank">http://github.com/Ponce/SBogit</a><br>
<br>
gotta say git is fun :D<br><br></blockquote><div><br></div><div>I'm interested with the idea -- use git to track a "branch" of SBo repo. Actually, I(together with vvoody) have a git repo to track our SlackBuilds: <a href="http://gitorious.org/slackbuilds">http://gitorious.org/slackbuilds</a></div>
<div><br></div><div>I'm also interested in how do the SBo admins do source control management ;) SVN, or just tarball backups?</div></div><br>-- <br>Cheers,<br>Grissiom<br>