18 Mar
2009
18 Mar
'09
11:55 a.m.
I haven't had a look at your package, but my advice is the following:
- if you have test unit that go green, and
- if you have few comments saying what the package is useful for
stored _in_ the package, it should be included in Moose, and finally,
- if you have no override
Alexandre
On 18 Mar 2009, at 11:50, Simon Denier wrote:
On 18 mars 09, at 11:45, Alexandre Bergel wrote:
--
_,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:
Alexandre Bergel http://www.bergel.eu
^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;.
Hi All,
I am slowing uncovering a problem with Moose-All. If I make a
package (let's say Moose-OBBrowser) and make it required to another
one (let's say Moose-All).
Before saving, I always check whether there is a new version in MC.
If there is one, I merge. But for some reason, merging remove the
dependency I just added.
I never had this problem but wow, that's a bug for MC
Simon, were you trapped by this? There is a
Moose-ModuleAlgorithms-
simon_denier.19 that is not loaded by Moose-All. Just wondering.
Nope, this package is not part of Moose-All right now, although it
should be one day.
--
Simon
_______________________________________________
Moose-dev mailing list
Moose-dev(a)iam.unibe.ch
https://www.iam.unibe.ch/mailman/listinfo/moose-dev