[Slackbuilds-users] git and stuff

[Willy Sudiarto Raharjo]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

> so obviously i've used the web form, but it seems that some people
> here mention their own git repositories for updates. what's that
> process like? i didn't see much mention of the 'official'
> slackbuilds git repository but google helped me find that. is there
> a preference one way or the other or is it best to just keep my own
> repo and pull from the official but "push" changes using the web
> form?

> i still only plan on making changes to those packages i maintain
> but i find i always download a copy from the site, make my changes,
> upload tar.gz. it'd be nice to just pull changes from the office
> onto mine.


Hi Miguel

yes, as you can see, we allow 'some' people to update their own
packages directly on SBo's GIT repository, thus it's easier for us to
just take their changes during public update and push it along with
other changes by other maintainers.

You can use this method as a start:
- - clone our GIT repository and push it to public space, such as github
or bitbucket or any other public git repo out there
- - make a branch based on latest master branch
- - make your changes on that branch
- - send me your pull request and i will merge it on my branch

during public update, you only need to pull master branch for updates
and then rebase your branch or simply create your branch and make a
new branch from updated master branch

I already use this method for Dimitris and Ryan and so far, it worked :)

> also, i'm assuming official really is 
> http://slackbuilds.org/cgit/slackbuilds/

this is just a tool to view changes happening on all branches
the official git is git://slackbuilds.org/slackbuilds.git


- -- 
Willy Sudiarto Raharjo
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2

iEYEARECAAYFAlQs7wkACgkQiHuDdNczM4F1ZgCbBhOkwloV0vs2ey8net6eItsj
2IEAnjYLYoM4rr5KlGmSyRY2H3nbXIkt
=Bibj
-----END PGP SIGNATURE-----