Neil Bowers writes:
> You could put the modules in Acme::, which is another way of saying
> “you can’t rely on this in any way”. For example if you think the
> module is going to be Yak::Shave, you’d create Acme::Yak::Shave. If
> the name settles down, then you can release a non Acme version. Then
All the suggestions so far are bang on -- I just have one more: prepan.org
is a great place to post your module and get early feedback on it!
Thanks! I appreciate all the suggestions. --Chris
On Sat, Dec 13, 2014 at 12:56 PM, Karen Etheridge wrote:
>
> All the suggestions so far are bang on -- I just have one more: prepan.org
> is a great place to post your module and get early feedback on it!
>
* Chris Marshall [2014-12-12 17:35]:
> I thought I read somewhere that there is a way to have
> a "non-comittal" CPAN module in the sense that there was a namespace
> that *would* allow one to delete a module rather than having it in
> perpetuity?
IIRC there was a change to PAUSE recently in whic
Hi Chris,
> I'm working on some new module development and I would like to make the
> progress available via CPAN and for testing, I don't want to start claiming
> package namespaces until things settle down.
>
> I thought I read somewhere that there is a way to have a "non-comittal" CPAN
> mo
On Fri, 12 Dec 2014 17:33:58 +0100, Chris Marshall
wrote:
All-
I'm working on some new module development
and I would like to make the progress available
via CPAN and for testing, I don't want to start
claiming package namespaces until things
settle down.
I thought I read somewhere that the
On 12/12/2014 11:38 AM, Yanick Champoux wrote:
On 14-12-12 11:33 AM, Chris Marshall wrote:
Else, any recommendations on how to
accomplish the goal of not locking in the
namespaces until the organization of the
various components settle down?
Just throwing ideas: an alternative would be to have
On 14-12-12 11:33 AM, Chris Marshall wrote:
> Else, any recommendations on how to
> accomplish the goal of not locking in the
> namespaces until the organization of the
> various components settle down?
Just throwing ideas: an alternative would be to have your module lives
on GitHub, and use the f
All-
I'm working on some new module development
and I would like to make the progress available
via CPAN and for testing, I don't want to start
claiming package namespaces until things
settle down.
I thought I read somewhere that there is a
way to have a "non-comittal" CPAN module
in the sense th
