comment on

(This is a continuation of Perl6 - Module::Build.)

After reading those replies, talking on #perl6, and emailing perl6-language, I've come to the following conclusions:

There is a problem with how the problemspace is being divided up. There seems to be a call for having a separate distro builder and distro installer.
Actually, there seem to be six separate components in the whole distribution management space:
1. Distro builder (ExtUtils::MakeMaker / Module::Build)
2. Distro installer / uninstaller (EU::MM / M::B)
3. Distro metadata inspector (No P5 analog)
4. Distro distribution center (C6PAN)
5. Distro up-/down-loader (Think CPAN/CPANPLUS and the cpan_upload script)
6. The 'use' and 'require' keywords
I include the latter because all 6 components need to be aware of S11.
Because of this, I suspect there's a seventh, shared component that controls how @*INC is searched and which of the competing options is selected.
That shared component needs to be mixin-able, with its Roles overridable. Because the way authoring/versioning metadata is stored will vary by OS, there needs to be OS-specific code in there.
A major issue, which apparently has not been discussed a lot, is how to implement the fact that Parrot (and any other VM P6 may target) will provide for multi-lingual distributions. The only comparison that exists is .NET, and that problem is solved by the fact that all the languages are under the same architecture team. We don't have that luxury.

Now, what I would like from the community:

What actions would you like to see from the various components? What would those actions entail? Would there be dependencies between actions? If so, could those dependencies be overriden (a la "perl -MCPAN -e 'force install Foo::Bar'")
Ideas regarding the Parrot dillema, particularly ideas crossposted to p6-language.
Comments on anything and everything I've posted so far.

In general, if you think something isn't in Perl, try it out, because it usually is. :-)
"What is the sound of Perl? Is it not the sound of a wall that people have stopped banging their heads against?"

In reply to Perl6 - Distribution builder/installer by dragonchild

Posts are HTML formatted. Put <p> </p> tags around your paragraphs. Put <code> </code> tags around your code and data!

Titles consisting of a single word are discouraged, and in most cases are disallowed outright.

Read Where should I post X? if you're not absolutely sure you're posting in the right place.

Please read these before you post! —

Posts may use any of the Perl Monks Approved HTML tags:

a, abbr, b, big, blockquote, br, caption, center, col, colgroup, dd, del, details, div, dl, dt, em, font, h1, h2, h3, h4, h5, h6, hr, i, ins, li, ol, p, pre, readmore, small, span, spoiler, strike, strong, sub, summary, sup, table, tbody, td, tfoot, th, thead, tr, tt, u, ul, wbr

You may need to use entities for some characters, as follows. (Exception: Within code tags, you can put the characters literally.)

	For:		Use:
	&		`&`
	<		`<`
	>		`>`
	[		`[`
	]		`]`

Link using PerlMonks shortcuts! What shortcuts can I use for linking?

See Writeup Formatting Tips and other pages linked from there for more info.