[Slackbuilds-users] Slackware 14
joshuakwood at gmail.com
Wed Aug 1 13:50:49 UTC 2012
On Aug 1, 2012 3:51 AM, "Petar Petrov" <ppetrov at mail.student.oulu.fi> wrote:
> Quoting Eric Hameleers <alien at slackbuilds.org>:
>> On 07/31/2012 08:37 PM, Petar Petrov wrote:
>>> Hi to all
>>> Since I joined SBo a year ago and have so far maintained scripts for
>>> only one Slackware release, I have the following question: What shall
>>> I do before the new Slackware release comes out? Am I supposed to
>>> start testing my slackbuilds when Slackware -current becomes RC1? Then
>>> if something needs patching, submit an update? The upload form is
>>> closed now, so what are you guys up to?
>>> Sorry if the questions sound silly, I read the mailing lists archives
>>> from a year ago when Slackware became 13.37, but did not find an answer.
>> Yes, that is the idea.
>> If you test your SlackBuilds against Slackware 14 RC and report success
>> (or send us updates) then that will help the admins immensely in getting
>> a Slackware 14 repository live at the time of release.
>> You will have noticed that with every new Slackware release, several
>> SlackBuilds.org entries will disappear. The reason for this is that the
>> maintainer has not reported whether his submission(s) work for the new
>> release. The SlackBuild database is so big these days that the admins
>> can no longer test all the scripts in the short time between closing the
>> submissions form and the new Slackware release. We rely on the
>> maintainers to tell us it's OK to copy scripts from one to the next
>> Cheers, Eric
>> SlackBuilds-users mailing list
>> SlackBuilds-users at slackbuilds.org
>> Archives - http://lists.slackbuilds.org/pipermail/slackbuilds-users/
>> FAQ - http://slackbuilds.org/faq/
> Thanks for the clarification Eric!
> I don't want to sound like "Are we there yet?", but are there any major
changes scheduled for Slackware14 yet to happen? Anything that I better
wait for, before I upgrade to -current and check how slackbuilds behave?
> SlackBuilds-users mailing list
> SlackBuilds-users at slackbuilds.org
> Archives - http://lists.slackbuilds.org/pipermail/slackbuilds-users/
> FAQ - http://slackbuilds.org/faq/
If possible, you should have a dedicated development machine for testing
your SlackBuilds. You should preferably have a virtual machine that you can
reset to a clean install state between tests. And you should at least test
in a chroot. Building on your desktop can be a valid test, but you really
need to know that what you maintain will build on a clean Slackware install
with only the noted dependencies installed.
You should preferably also test out the functions of the program just to
make sure you didn't miss any optional or runtime dependencies.
Remember, the more and higher quality testing you do, the less likely it is
that you have to scramble to fix foreseeable bugs.
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the SlackBuilds-users