search

Ponce / SBo-git

WARNING: developing is moved on the slackbuilds.org's git fork - http://github.com/Ponce/slackbuilds - repository kept for historical reasons only :)
http://slackware.ponce.cc/blog/
5 stars 0 forks source link

ways to cooperate with official git repo #3

Open grissiom opened 14 years ago

grissiom commented 14 years ago

As SBo admins announced their git repo to the public, maybe we should follow it. Is there any way to cooperate with it? Or just migrate to it totally?

Ponce commented 14 years ago

I cloned their master branch locally, pushed to github and started moving the branches they haven't fixed yet on this github clone (following Robby advices), but I also will put there a new branch for x264, a new branch for ffmpeg and other stuff I need (like in the old repo):

http://github.com/Ponce/slackbuilds

then I think I'll do a new "ponce" or "current" branch in which I'll merge all the other branches to have a fully patched branch to sync with sbopkg.

I think we better refeer to robby mails about handling it and to the commits they're doing now to give our commits the look they want (and also to apply some common fixes, like removing of ARCH definitions from the slackbuilds and so on) :)

http://lists.slackbuilds.org/pipermail/slackbuilds-users/2010-May/005627.html http://lists.slackbuilds.org/pipermail/slackbuilds-users/2010-May/005652.html

I don't think we can directly use this repository for that so I think migration is forced.

but I like their repository more, it's cleaner, just like we want ;)

grissiom commented 14 years ago

Hmm, yes. If we base all of our work on the official repo, what is this repo for?

Ponce commented 14 years ago

historical reasons: first sbo repo on git :D

grissiom commented 14 years ago

That's cool ;-)