Re: About putting the blame on other shoulders

[prev] [thread] [next] [Date index for 2004/12/28]

From: merlyn (Randal L. Schwartz)
Subject: Re: About putting the blame on other shoulders
Date: 16:43 on 28 Dec 2004
>>>>> "Stas" == Stas Bekman <stas@xxxxxx.xxx> writes:

Stas> Unfortunately thanks to Randal, people are now totally confused.

No, I think thanks to me, people are now aware of a problem of
fundamental incompatibility between the "single @INC" historical
legacy of the entire Perl world and toolchain, and your "use Apache2"
workaround.  There's awareness, not confusion.  I think *you* are
trying to confuse the issue by saying there's not a single thing wrong
with your proposed release of MP2.  Yes, there wouldn't be, if the
entire rest of the world was compatible with it, which it isn't.

Here are some possible scenarios:

1) you don't budge, CPAN doesn't change, and people around the world
get confused with your release, because it's asking them to "upgrade"
their mp1 by installing mp2, which *cannot* be done.

2) you don't budge, the rest of the world changes, toolsets get altered,
everyone upgrades their tools just to avoid #1.  I think this is
what you want, but a lot of resources and a lot of people have to bend
to your beck and call to make this happen, and it's not gonna happen
by mid January.

3) you don't release mp2 to the CPAN except as an "experimental" version
number, which avoids indexing, and people who want it can ask for it
by name directly, not via "install mod_perl".

4) you figure out how to rename all mp2 modules that aren't upward
implementation compatible with mp1 to a new namespace, and release
that like any of the other 72,000 modules on the CPAN.

5) something else entirely.

I'm just saying that #1 and #2 are both unacceptable to me.  I think
it's also unacceptable to a lot of others.  So we need to look at #3,
#4, and #5.

Now, if everyone involved agrees that #1 or #2 are workable, that's
fine too.  But I want this to be a community decision, not just "Stas
forcing pollution into everyone else's lives".

        -- 
        Randal L. Schwartz - Stonehenge Consulting Services, Inc. - +1 503 777 0095
<merlyn@xxxxxxxxxx.xxx> <URL:http://www.stonehenge.com/merlyn/>
Perl/Unix/security consulting, Technical writing, Comedy, etc. etc.
See PerlTraining.Stonehenge.com for onsite and open-enrollment Perl training!

-- 
Report problems: http://perl.apache.org/bugs/
Mail list info: http://perl.apache.org/maillist/modperl.html
List etiquette: http://perl.apache.org/maillist/email-etiquette.html

(message missing)

Re: Slashdot | Help Test mod_perl 2 Release Candidates
merlyn (Randal L. Schwartz) 20:34 on 26 Dec 2004

Re: Slashdot | Help Test mod_perl 2 Release Candidates
merlyn (Randal L. Schwartz) 15:09 on 27 Dec 2004

About putting the blame on other shoulders
Andreas J Koenig 14:28 on 28 Dec 2004

Re: About putting the blame on other shoulders
Stas Bekman 15:01 on 28 Dec 2004

Re: About putting the blame on other shoulders
Stas Bekman 15:54 on 28 Dec 2004

Re: About putting the blame on other shoulders
Andreas J Koenig 16:11 on 28 Dec 2004

Re: About putting the blame on other shoulders
Issac Goldstand 16:11 on 28 Dec 2004

Re: About putting the blame on other shoulders
Stas Bekman 16:27 on 28 Dec 2004

Re: About putting the blame on other shoulders
merlyn (Randal L. Schwartz) 16:43 on 28 Dec 2004

Re: About putting the blame on other shoulders
Issac Goldstand 16:58 on 28 Dec 2004

Re: About putting the blame on other shoulders
merlyn (Randal L. Schwartz) 17:09 on 28 Dec 2004

Re: About putting the blame on other shoulders
Issac Goldstand 17:30 on 28 Dec 2004

Re: About putting the blame on other shoulders
David Nicol 07:01 on 30 Dec 2004

Generated at 12:15 on 16 Jan 2005 by mariachi v0.52