<br><br><div class="gmail_quote">On Thu, May 15, 2008 at 2:21 PM, Robby Workman <<a href="mailto:rworkman@slackbuilds.org">rworkman@slackbuilds.org</a>> wrote:<br><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
<div class="Ih2E3d">Phillip Warner wrote:<br>
<blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
I personally have no problem with that, but some people may and this might discourage some good submissions. Perhaps a good compromise would be to make sure it doesn't sound too harsh or if it is only for one Slackware release. If the next release comes out and the maintainer doesn't update a script that doesn't work on the newest release, then it can simply be removed. It would be nice if maintainers would let us know when they no longer can/want to maintain a slackBuild, so maybe this could be asked of the person submitting a script.<br>
<br>
Something that also might be really useful is to start an official list of orphaned and recently removed scripts. That way a person could look at that one file and then email the user list to say "Hey, I'll take it. Here's my submission." I know this could be accomplished through threads like this, but it might be more convenient to have it all in once place instead of spread through many messages. Ideally, this would be included on the site similar to the Changelog, but I understand if the admins don't want another file to maintain.<br>
</blockquote>
<br>
<br></div>
We were just talking about doing something like that - we think it<br>
will help *us* too :)<br><font color="#888888">
<br>
-RW</font><div><div></div><div class="Wj3C7c"><br>
_______________________________________________<br>
Slackbuilds-users mailing list<br>
<a href="mailto:Slackbuilds-users@slackbuilds.org" target="_blank">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>This is why I never submitted any of my SlackBuilds for mjpegtools, or DVDStyler + it's other depends. I wouldn't want to submit something, and not be able to maintain it. Not exactly wise for myself to do, considering I've only just switched back to Slackware a few months back. As it stands now, I have no plans of using another distro. But that's what I said with 10.0(.1?) and Vector, and Debian, and Ubuntu, and ..... ;)<br>
<br>Seems like the SlackBuilds team has enough work as it is. <br><br>Take a look at Arch Linux's AUR to see what orphaned build scripts can cause. A bunch of unmaintained build scripts of older software missing updates/fixes and not compatible with the current release. They also run into problems with 3-4 different build scripts of the same software.<br>