On Fri, May 28, 2010 at 1:32 PM, xgizzmo <[email protected]> wrote: > On Fri, May 28, 2010 at 12:23 PM, Matthew Fillpot <[email protected]> wrote: >> Having a current branch in git only (not having it visible to the website) >> will help to have preparations done for the upcoming releases. Although not >> all maintainers will not be able to keep it current, it would be useful to >> reduce load on the sbo team when new releases are pushed. >> >> On May 28, 2010 12:03 PM, "Ozan Türkyılmaz" <[email protected]> >> wrote: >> >> 2010/5/28 Grissiom <[email protected]>: >> >>> Hello all, >>> It's exciting to hear and see that SBo team have a public git repo now(You >>> have SCM... >> >> if there will be a repo for current, i won't able to maintain any package >> for it >> on grounds of lack of time. current changes too much too fast, and keeping >> track of it is itself a big job. >> >> -- >> Ozan >> _______________________________________________ >> SlackBuilds-users mailing list >> [email protected] >> http://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users >> Archives - http://lists.slackbuilds.org/pipermail/slackbuilds-users/ >> FAQ - http://slackbuilds.org/faq/ >> >> >> _______________________________________________ >> SlackBuilds-users mailing list >> [email protected] >> http://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users >> Archives - http://lists.slackbuilds.org/pipermail/slackbuilds-users/ >> FAQ - http://slackbuilds.org/faq/ >> >> >> > I don't not speak for the whole admin staff. But I feel it is almost > pointless to try and maintain anything based on -current. You will > expend tons of time doing it, and run the risk of having everything > you worked on being undone by a single up date to -current. If we made > a -current repo then we would be forced into keeping it up to date > with -current, something I do not intend to do. > _______________________________________________
I agree... -current is a "moving target". I have a machine running current all the time, and all the time things change. Look what changed between 13.0 and 13.1 that affected SlackBuilds: - new bash - new libpng - new gcc - ... and some other stuff... The first three items alone caused work for several SlackBuilds. If SBo creates a public repository (even if it's only git, not http), people expect it to be stable, which it will almost never be. My two (Brazilian) cents... Niels _______________________________________________ SlackBuilds-users mailing list [email protected] http://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users Archives - http://lists.slackbuilds.org/pipermail/slackbuilds-users/ FAQ - http://slackbuilds.org/faq/
