I would also point out that if the package hasn't been updated in the official git repository, it might have been updated in the unofficial -current repository on github.<br><br><br><div class="gmail_quote">On Wed, May 26, 2010 at 9:01 PM, King Beowulf <span dir="ltr"><<a href="mailto:kingbeowulf@gmail.com">kingbeowulf@gmail.com</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="margin: 0pt 0pt 0pt 0.8ex; border-left: 1px solid rgb(204, 204, 204); padding-left: 1ex;">I appreciate the hard work of all the SBo admins. So tale your time.<br>
Its not like I can install 13.1 yet anyway - its d/l via bittorent and<br>
then I had to hop a plane for work. Also, on behalf of some whiner<br>
slackers ("are we there yet? NO!!), I apologize for all their<br>
impatience.<br>
<br>
And while I'm on a rant, why can't those lazy bastards just TRY the<br>
13.0 slackbuild on 13.1 (as some have, kudos)? Maybe these kids would<br>
rather go with Ubuntu?<br>
<br>
-Ed<br>
<div><div></div><div class="h5"><br>
<br>
On 5/25/10, Robby Workman <<a href="mailto:rworkman@slackbuilds.org">rworkman@slackbuilds.org</a>> wrote:<br>
> I know there's a bit of anticipation by now, and probably some<br>
> pondering as to why we haven't got a set of scripts out there<br>
> for 13.1 yet, so I guess some explanation/discussion is in<br>
> order...<br>
><br>
> Basically, the Slackware 13.1 release snuck up on us (yes, even<br>
> though several of the SBo admin team *knew* it was coming), and<br>
> it happened to coincide with real-life conflicts for several of<br>
> the admins, so we didn't get as far along with preparation as we<br>
> normally would have. Because we believe that, like Slackware,<br>
> it should only go public "when it's ready," we decided to wait<br>
> until we were comfortable calling things "ready" for public<br>
> consumption before spinning tarballs and such and putting out<br>
> a public changelog in the usual manner.<br>
><br>
> The other major factor that's played a part in the delay is<br>
> something that lots of people have long requested, and that<br>
> is tracking the repository in git. Yes, that's right - we<br>
> now have a git repo with everything in it. Consider the ensuing<br>
> comments to be NON-FINAL, NON-BINDING, and SUBJECT TO CHANGE<br>
> based on feedback, our preferences, logistics, phase of the<br>
> moon, and various other known and unknown factors...<br>
><br>
> <a href="http://slackbuilds.org/gitweb/" target="_blank">http://slackbuilds.org/gitweb/</a> has a web interface to the<br>
> git repositories - you will notice that there is a 'slackbuilds'<br>
> repo and a 'templates' repo, and each of them contains exactly<br>
> what the name implies.<br>
><br>
> The 'slackbuilds' repo contains several "predictable" branches:<br>
> 11.0, 12.0, 12.1, 12.2, 13.0, and 13.1, and each of those has<br>
> exactly what the branch name implies. It's a bit early to be<br>
> setting anything in stone, but unless something changes, the<br>
> '13.1' branch at any given moment should be the equivalent of<br>
> what is available on the website (in other words, it's exactly<br>
> what you would have gotten from an rsync of the slackbuilds/13.1/<br>
> tree if we didn't have a git repo).<br>
><br>
> Each admin will have one or more separate branches (which might<br>
> have various names) where he will push approved submissions as<br>
> they are cleared. From time to time, one of us will gather the<br>
> various commits from the admin-specific branches and commit them<br>
> to master, and once we decide to do a public push to http (the<br>
> "old" way of doing things), then we'll merge master into the 13.1<br>
> branch, generate the tarballs, gpg sigs, and ChangeLog, and sync<br>
> that over to the http tree. Again, the http tree (the old way)<br>
> will always be in sync with the 13.1 branch (until 14.0 is out).<br>
><br>
> For those of you who don't know git and/or have no desire to learn<br>
> it, fear not -- nothing changes with respect to the rest of our<br>
> site. Everything stays the same in regard to rsync, ftp, http,<br>
> and so on.<br>
><br>
> For those of you who *do* know/use git, this is another option for<br>
> you. For the time being, submissions will still be done using the<br>
> existing method - git pull requests are not an option right now. [1]<br>
><br>
> This probably doesn't need to be said, but for your own sanity,<br>
> DO NOT base any work on an admin-specific branch (e.g. on my<br>
> 'rworkman' branch) -- those are subject to be rebased, removed,<br>
> etcetera at any time.<br>
><br>
> Anyway, we hope to have all the kinks ironed out of this soon,<br>
> and once we do, we'll get everything up and running normally.<br>
> Thanks for your support and patience, and in the meantime,<br>
> enjoy 13.1!<br>
><br>
> [1] That's not to say that a git pull request won't be honored.<br>
> In fact, if you were to clone master and host it on e.g. github,<br>
> and create a separate branch for each app that you submit via<br>
> our submission form, and note that in the comments of the<br>
> submission, it's certainly possible that some of us :) might<br>
> use that. This is particularly true for cases where:<br>
> [ $admin == rworkman ] && [ $changetype == trivial ] :-)<br>
><br>
> -RW<br>
><br>
<br>
</div></div><div class="im">--<br>
Sent from my mobile device<br>
<br>
You! What PLANET is this!<br>
-- McCoy, "The City on the Edge of Forever", stardate 3134.0<br>
_______________________________________________<br>
</div><div><div></div><div class="h5">SlackBuilds-users mailing list<br>
<a href="mailto:SlackBuilds-users@slackbuilds.org">SlackBuilds-users@slackbuilds.org</a><br>
<a href="http://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users" target="_blank">http://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users</a><br>
Archives - <a href="http://lists.slackbuilds.org/pipermail/slackbuilds-users/" target="_blank">http://lists.slackbuilds.org/pipermail/slackbuilds-users/</a><br>
FAQ - <a href="http://slackbuilds.org/faq/" target="_blank">http://slackbuilds.org/faq/</a><br>
<br>
</div></div></blockquote></div><br>