On Sep 21, 2009, at 11:02, Marc G. Fournier wrote:
> Chris, you live!!
I replied on Sept. 18 to your private email last week.
> Okay, "we use" ...? who is we? I've tried MySQL 5.1 -> 5.0 and
> gave up and went down to 4.0 before I could get the data to load ...
> seemed to be just a change in the schema, but hadn't had a chance
> yet to
> dive into it ...
It could be there's problems with the old data dumps. I don't know.
The code works fine.
> As to Apache 2 ... I haven't played with it with Slash yet, but ti
> shouldn't be a whole lot of changes to make it work, should it? Or
> is it
> just mod_perl that is the hang up?
We hook into many parts of the Apache 1.x cycle, and it's changed
significantly in 2.x. (Not to mention, of course, being a completely
different type of server, we'd have to expend significant resources
into figuring out how best to configure and deploy the servers for our
needs. No small task there.)
> As for 'newer' perl ... I'm running on 5.8.9, and the only issue I
> was taht the newer Schedule::Cron 0.99 doesn't seem to have a public
> build_init_queue function, only an internal _build_init_queue ... I
> had to
> revert down to 0.97 to get around it, and everything else *seems* to
> okay with 5.8.9 ... so, from what I could tell, only that needs a
> tweak to
> run with newer Perl, but maybe taht is already fixed in the public
I am not sure where that function would be called, or what that has to
do with different perl versions.
> What public repo? I looked for that too ... the site mentions
> http://cvs.slashcode.com, but that just brought me back to the main
Yeah the URLs changed. Right now it is on (and out of date) on
github. I want to put it on SourceForge too. And I want it done this
week or next. Stay tuned. It's something we've pushed to fix up in
the last month or so, and I hope it's done soon.
> What can *we*, as a community, do to get things moving again? Get a
> release put out?
I do not anticipate any releases. We simply do not have the
resources. That said, if people wanted to make releases based on our
code, we'd be willing to provide some basic support. If it were me
working outside the Slashdot team making a release -- I've done
something like this in the past, with MacPerl -- I'd make the slash
repo a subdirectory of my release directory (or vice versa), so I can
keep those sources up to date separately, and then add whatever else I
wanted to the release in the separate directories: themes, Postgres
If someone is interested in this, the only thing I'd request is that
you discuss the name with us before releasing ... the company owns the
naming rights to some degree and I don't know how to deal with that.
But the rest of the code is open, so knock yourself out.
Most of what is being discussed would not require a fork; even Apache2
support, being mostly in a few modules, could be perhaps designed as
drop-in replacements (and patches to the main codebase requiring a
small amount of work to such ends would be welcome).
Chris Nandor pudge@... http://pudge.net/
Slashdot / SourceForge pudge@... http://slashdot.org/