in reply to Re^3: When is it better to NOT release a new module?
in thread When is it better to NOT release a new module?
Its much less sane to do that when you're releasing things onto CPAN where it will have to deal with anything that's potentially available.Excuse me? Since when is it a requirement that anything released on CPAN needs "to deal with anything that's potentially available"? Answer: never.
CPAN never has, and never will put any requirements on the code stored there, other than its license should allow distribution. If there were such requirements, we wouldn't have a gazillion Class::* modules, many of which don't play nice with each other.
If you don't want to use source filters - don't. Just don't go on a crusade claiming they are universally evil and people shouldn't put modules on CPAN that use source filters. CPAN is open for everyone - and that includes open for code that uses techniques you don't like.
|
|---|
| Replies are listed 'Best First'. | |
|---|---|
|
Re^5: When is it better to NOT release a new module?
by diotalevi (Canon) on Nov 03, 2005 at 14:24 UTC | |
|
Re^5: When is it better to NOT release a new module?
by diotalevi (Canon) on Nov 03, 2005 at 14:41 UTC |