<br><br><div class="gmail_quote">On Fri, May 28, 2010 at 9:16 PM, Kevin Pulo <span dir="ltr"><<a href="mailto:kev@pulo.com.au">kev@pulo.com.au</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;">
<div class="im">On Fri, May 28, 2010 at 02:59:29PM -0300, Niels Horn wrote:<br>
<br>
> If SBo creates a public repository (even if it's only git, not http),<br>
> people expect it to be stable, which it will almost never be.<br>
<br>
</div>I have to say, I really don't understand this.<br>
<br>
If Pat is able to make -current public, and people understand that<br>
it's explicitly not stable, then why can't SBo have a -current branch<br>
that is also understood to be completely and utterly unstable. When I<br>
choose to run -current, I know that all bets are off. To expect<br>
stable SBo scripts for an unstable distro branch is unreasonable.<br>
<br>
It is true that a lot of work may be lost when -current updates, but<br>
the people doing that work are likely to be the ones investing time<br>
into -current anyway (since they're tracking it for their own usage),<br>
so they are still getting benefit from having their scripts working in<br>
the time before the update. This way, it may save some others time.<br>
Also, feature changes from version upgrades (eg. bash4) tend to be<br>
once-off things that aren't reverted, and will need to be done come<br>
the next stable version anyway.<a href="http://github.com/Ponce/SBo-git">http://github.com/Ponce/SBo-git</a><br>
<br>
Kev.<br></blockquote><div><br>I agree with most of the points you're making, however it's not *our* time/effort that we should be thinking about but the time/effort of the SBo team. They're busy guys (and I very much appreciate all the work you guys are doing!) and their time is valuable. Asking them to manage an official -current repository on top of all the good work they're already doing for Slackware and SBo seems a bit unreasonable. <br>
<br>There is already an unofficial repository for -current on GitHub. I suggest that those of us who are interested in following the tip of -current should contribute our efforts to the unofficial -current tree. The SBo team always has the option to pull from that tree if they see fit. Thanks to the distributed nature of Git, there is nothing stopping us from collaborating on slackbuilds for -current even if the authors of the official tree choose not to.<br>
<br>I see <a href="http://slackbuilds.org/gitweb/">http://slackbuilds.org/gitweb/</a> and <a href="http://github.com/Ponce/SBo-git">http://github.com/Ponce/SBo-git</a> as being complementary (not competing) projects. <br>
<br>My $0.02.<br><br>Regards,<br>Ben<br></div><blockquote class="gmail_quote" style="margin: 0pt 0pt 0pt 0.8ex; border-left: 1px solid rgb(204, 204, 204); padding-left: 1ex;">
<br>
<br>_______________________________________________<br>
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>
<br></blockquote></div><br>