Op 31-05-13 22:14, Marcel de Rooy schreef:
Could you give some steps or add a wiki page for such ?
Or should I just leave it to you :)
It's all good, it gets picked up whenever I run the update-control script, which in an ideal world I do every release. It's minorly preferable to not introduce dependencies in the middle of a release as it causes a little bit of pain doing apt-get upgrade (apt won't pull in new dependencies without being told to by running dist-upgrade) but if it's something important, that's OK. And if it's only going into master, that's perfectly fine. On this note, it's also best to use modules that are packaged in Debian squeeze (which I figure we'll try to support as long as we can) where possible, just to save me the work in making packages for them :) Also, cpan modules that have no license that allows us to redistribute them are a no-no. This doesn't apply to libemail-valid-perl however, it's in squeeze already. Tot ziens, Robin.