Re: [Slashcode-general] Jumping in here late ... Slashcode is Dead ...

[Shane Z. <sh...@lo...>]

On Sep 21, 2009, at 3:19 PM, Axel Beckert wrote:

> Hi,
>
> great to see that not all people lost hope. :-)
>
> On Mon, Sep 21, 2009 at 01:56:43PM -0300, Marc G. Fournier wrote:
>> My prior desire is to modernize the technology ... newer perl, newer
>> apache, newer mysql, improved postgresql support ... to me, those  
>> are the
>> easy parts though ...
>
> There is a patch from 2004 at
> http://www.crackerjack.net/slash-2.2.6-modperl2.diff.txt against the  
> last
> stable release 2.2.6.
>
> Another thing Slashcode needs (at least WRT the public) is a release
> management. Proper stable releases and changelogs. This will help
> people who package software for distributions a lot.

We did come up with a system for automated updates. We used it on our  
slash-hosting environment for years; We even upgraded a number of  
clients from the pre (2.2.6) to cvs-HEAD (at the time) using the tools.

A few years ago I think I did package them up and sent them (or bits  
and pieces) to someone from the OSTG Slashcode crew for perusal. I  
don't honestly recall what ever happened with it; I'm fairly certain  
some of the patches I wrote/wanted/submitted to the Slash::Install  
module made it into the public tree. Some didn't. (An example was  
recursive slash.conf calls, I think it turned out modding the  
installer was a bit more of a task to make it work then what I had  
time to contribute towards that). The update system's code, while  
functional, was just never finished "aka cleaned up and releasable" by  
me. It "worked for us" (in about 2 minutes time we were able to update  
an entire slash-farm on a weekly basis) and that was enough, and we  
had to move on towards other money making ventures.

I have "finish, clean and put up on github" on my todo list for it,  
when there's this thing called "Freetime" that I'm not finding too  
often. Maybe someday.

  Shane