develooper Front page | perl.perl5.porters | Postings from June 2006

Re: Saner installation. (Was: perl5 FUD hell-thread.)

From:
James Mastros
Date:
June 19, 2006 07:25
Subject:
Re: Saner installation. (Was: perl5 FUD hell-thread.)
Message ID:
20060619142507.GE24801@desert-island.dynodns.net
On Mon, Jun 19, 2006 at 09:58:41AM -0400, John Peacock wrote:
> James Mastros wrote:
> >Then we can add "os:", "header:", and "executable:" spaces, and make the
> >rule that older installers, when faced with a space they don't know how to
> >handle, should warn on all requirements in it, but otherwise ignore them 
> >(IE
> >assume they are satasified for everything but "conflicts".)
> 
> The problem is that the energy required to open a blackhole so older 
> installers could be altered worldwide is beyond the limits of current 
> technology.  Nice idea, though... ;-)
Apparently, I didn't explain myself very well, sorry.  The idea is to switch
from the "foo" keys in META.yml to "foo-2" keys.  Think of three different
ages of installers, when we hypothetically move forward with my plan, and
then introduce another space, foo:.

1. Those that do not know about the requires-2 key.
   - They will live in blisfull ignorance, and continue to use the requires
     key, which only lists perl modules.
2. Those that do not know about the foo: space.  They follow the rules set
   down in my email, and thus ignore the foo: space (with a warning).
3. Those that know about the foo: space.  They do whatever they should.

"older installers" in the context you quoted above refers to 2, not 1.

       -=- James Mastros



nntp.perl.org: Perl Programming lists via nntp and http.
Comments to Ask Bjørn Hansen at ask@perl.org | Group listing | About