D'oh!

I think the naming convention here is entirely unfortunate. That it lines up with, say, Debian's installer, is not a redeeming feature to me. If I were to use an install program, alone, to install Task::Foo, or whatever Debian uses, that's one thing. The install namespace probably doesn't collide with anything else.

However, this namespace also happens to be shared with actual code namespaces. Personally, I'd rather see Bundle:: fixed than see this. Even then, doing anything along these lines seems to just perpetuate the hack of reusing the install/code namespace for purely install purposes.

Why am I so concerned? I already have a whole Task namespace at work, with a Task manager packager, and a base Task package, which all my tasks are derived from, and if I had ever thought about sharing it with CPAN, I wouldn't really want to rename it if possible. So I would have a huge collision in sharing this piece of our infrastructure.

Be careful when introducing new top-level namespaces. Be even more careful when it's not for code. If you need a new namespace, I would have suggested Install or, even better, BundleInstall or something that was more in line with what you're doing. Task isn't it - task is something you do, and it's not a leap of logic to assume that code would do something, and those could be tasks.

You're not just colliding with our code in surprising ways, you're colliding with our ability to use anyone whose bundles follow your convention. Not preventing us from doing so, but definitely making it a bigger headache than if you picked a better namespace.

In reply to Re: Task:: - The successor to Bundle:: for installing sets of modules by Tanktalus
in thread Task:: - The successor to Bundle:: for installing sets of modules by Anonymous Monk

Title:
Use:  <p> text here (a paragraph) </p>
and:  <code> code here </code>
to format your post, it's "PerlMonks-approved HTML":


  • 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:
    & &amp;
    < &lt;
    > &gt;
    [ &#91;
    ] &#93;
  • Link using PerlMonks shortcuts! What shortcuts can I use for linking?
  • See Writeup Formatting Tips and other pages linked from there for more info.