Re: rfc: a generic solution for dual-life CPAN packages

2003-03-31 Thread Michael G Schwern
On Mon, Mar 31, 2003 at 01:44:41PM +1000, Stas Bekman wrote: I need to release Apache::Test on CPAN and I can't do that, because of the bundling problem. I don't know how many man-months very spent on writing the current mod_perl 2.0's build, and while it'd be cool to move to Module::Build

Re: rfc: a generic solution for dual-life CPAN packages

2003-03-31 Thread Graham Barr
On Sat, Mar 29, 2003 at 07:46:19PM +0800, Autrijus Tang wrote: Am I correct to assume that, if all such files are explicitly excluded from indexing via META.yml, then search can skip them altogether? If so, there's no need for hard-coding inc/ either within the indexer or in Module::Install

Re: rfc: a generic solution for dual-life CPAN packages

2003-03-28 Thread Ken Williams
On Thursday, March 27, 2003, at 08:36 PM, Stas Bekman wrote: The more I think about it the more I like my latest idea. I'm going to expand on it in this post as I think it may do more things than just solving the bundling problem. What I'm proposing is to have a mechanism similar to /robots.txt

Re: rfc: a generic solution for dual-life CPAN packages

2003-03-28 Thread Graham Barr
On Fri, Mar 28, 2003 at 05:54:52PM +0100, Andreas J. Koenig wrote: Note that this solution isn't specific to Module::Build, it just relies on using a META.yml description file. The META.yml file ideally will make the work, that's currently done by the PAUSE indexer, unnecessary.

Re: rfc: a generic solution for dual-life CPAN packages

2003-03-28 Thread Autrijus Tang
On Fri, Mar 28, 2003 at 01:24:37PM +1100, Stas Bekman wrote: Why this is beneficial to the /inc solution: - it's flexible and not hardcoded, casted in stone, solution This I agree. However I'd argue for a default INDEX (in case that the distribution does not come with one) that includes at

Re: rfc: a generic solution for dual-life CPAN packages

2003-03-27 Thread Christopher Hicks
On Thu, 27 Mar 2003, Stas Bekman wrote: Please, can we stay focused in this thread on the generic problem that I'm trying to solve? I think this problem relates to the CPAN.pm bug we've seen reoocur several times where it tries to upgrade perl. This is one of the biggest complaints I've

Re: rfc: a generic solution for dual-life CPAN packages

2003-03-27 Thread Jos I . Boumans
In [EMAIL PROTECTED] Ken Williams wrote: Ideally, I think, CPAN or CPANPLUS would tell the user the requested module is available in the following distributions, which one do you want to install?. Although that would perhaps be a nice feature to have according to some ( although i feel it

Re: rfc: a generic solution for dual-life CPAN packages

2003-03-27 Thread Autrijus Tang
On Thu, Mar 27, 2003 at 08:19:49AM +0100, Andreas J. Koenig wrote: Maybe Autrijus can comment on the time frame that Module::Install will need until it will be available for wide public use. I'd expect that you will like it for mod_perl. A preview version has been uploaded as

Re: rfc: a generic solution for dual-life CPAN packages

2003-03-27 Thread Autrijus Tang
On Fri, Mar 28, 2003 at 10:04:50AM +1100, Stas Bekman wrote: First of all, is that how indexer works today? Apparently yes. Is that documented as a public interface, so it won't change in the future? Second, as Autrijus followed up, it seems that it's not going to be inc. I love the name

Re: rfc: a generic solution for dual-life CPAN packages

2003-03-27 Thread Stas Bekman
The more I think about it the more I like my latest idea. I'm going to expand on it in this post as I think it may do more things than just solving the bundling problem. What I'm proposing is to have a mechanism similar to /robots.txt in the HTTP protocol, where '/' is the root of the web server

Re: rfc: a generic solution for dual-life CPAN packages

2003-03-26 Thread Ken Williams
On Tuesday, March 25, 2003, at 09:43 PM, Stas Bekman wrote: Currently CPAN.pm has a special logic to make sure that if a requested package is found in the core perl distribution and in another package, that another package takes the precedence if its VERSION number is the same or higher than

Re: rfc: a generic solution for dual-life CPAN packages

2003-03-26 Thread Graham Barr
On Wed, Mar 26, 2003 at 08:31:25AM -0600, Ken Williams wrote: My recommendation would be to not include the helper package in the two core packages, and to just add it as a dependency. Even if CPAN were changed in the way you suggest, it wouldn't work properly with people's stock CPANs,

Re: rfc: a generic solution for dual-life CPAN packages

2003-03-26 Thread Andreas J. Koenig
On Wed, 26 Mar 2003 14:43:26 +1100, Stas Bekman [EMAIL PROTECTED] said: Once we have this logic in place, we no longer need to make a special case for the perl core, but let every package that has a dual (or a ternary) life define its master package. I'm sorry, I cannot follow you. Can

Re: rfc: a generic solution for dual-life CPAN packages

2003-03-26 Thread Stas Bekman
Andreas J. Koenig wrote: On Wed, 26 Mar 2003 14:43:26 +1100, Stas Bekman [EMAIL PROTECTED] said: Once we have this logic in place, we no longer need to make a special case for the perl core, but let every package that has a dual (or a ternary) life define its master package. I'm sorry, I

Re: rfc: a generic solution for dual-life CPAN packages

2003-03-26 Thread Stas Bekman
Ken Williams wrote: On Tuesday, March 25, 2003, at 09:43 PM, Stas Bekman wrote: Currently CPAN.pm has a special logic to make sure that if a requested package is found in the core perl distribution and in another package, that another package takes the precedence if its VERSION number is the

Re: rfc: a generic solution for dual-life CPAN packages

2003-03-26 Thread Ken Williams
On Wednesday, March 26, 2003, at 06:01 PM, Stas Bekman wrote: As Andreas correctly points out, it's the indexer thing, not the client CPAN.pm or CPANPLUS. So this change is transparent to users having whatever version of CPAN/CPANPLUS they have. I see. [I think I missed Andreas' message on

rfc: a generic solution for dual-life CPAN packages

2003-03-25 Thread Stas Bekman
Currently CPAN.pm has a special logic to make sure that if a requested package is found in the core perl distribution and in another package, that another package takes the precedence if its VERSION number is the same or higher than the VERSION number of that package in the core perl distro.