Re^2: Upgrading CPAN

could you add alternate (disjunctive) module dependencies, where a module can depend on different combinations of other modules (and module versions)?

This is Perl. Of course we can :P

Actually I'm sure that it's possible simply by extending the grammar or perhaps even with something like this:

use any(qw( ModuleA ModuleB ModuleC ));
[download]

Comment on Re^2: Upgrading CPAN - Yes We Can Download Code

Replies are listed 'Best First'.
Re^3: Upgrading CPAN - Yes We Can by ambrus (Abbot) on Jun 04, 2009 at 16:43 UTC
No, I mean dependencies the CPAN installer handles, so that when a module is installed it installs all the dependencies as well. (There are two varieties of these: dependencies that are only needed for building and that need to be permanently installed, but that is irrelevant now.) The difficult part with these is that you don't want to make everyone update their CPAN package, so the only way this could go is that the info file of new modules can contain both the old style dependencies (which is just a plain conjunction of versioned modules) and new style ones. However, as ExtUtils::MakeMaker generates the info file from Makefile.PL, it could also write a sensible default for the old style if you give a dependency expression that has disjunctions in it.	[reply]
Re^4: Upgrading CPAN - Yes We Can by jdrago_999 (Hermit) on Jun 04, 2009 at 17:15 UTC
I don't think I understand what you are saying. Are you talking about (for example) if you use Module::Install how you can say: `requires 'My::Module' => 1.02;` ...or... `test_requires 'My::Module' => 1.02;` ...but not: `requires_any => ( 'My::Module' => 1.02, 'My::OtherModule' => 2.33, );` [download] I suppose that the `requires_any` kind of logic could be implemented simply as a Module::Install plugin.	[reply] [d/l] [select]


No such thing as a small change
	PerlMonks

Re^2: Upgrading CPAN - Yes We Can