[Nagiosplug-devel] Extra opts help text

Andreas Ericsson ae at op5.se
Fri Apr 16 11:08:12 CEST 2010


On 04/16/2010 10:19 AM, Ton Voon wrote:
> 
> I'm not keen on auto download from CPAN because that means the version
> of N::P is decided at dist time and is not recorded. At least with the
> tarballs, we know exactly which version of N::P is included with which
> particular np. Also, dependent modules would be updated underneath you.
> 
> Then again, if someone was installing nagiosplug and N::P
> independently, there'd be no version dependency checking either.
> 
> I think the tarball is a better way. Don't think of it as "undiffable"
> differences, rather as recording the name and versions of dependent
> libraries.
> 

You'd save a lot on size and clutter if you tar them up but not compress
them in that case. Uncompressed tarballs delta just fine (although the
diffs are usually no fun to look at).

I'd sort it out with a 3-branch system; "master" which holds the "normal"
plugin code, "tarballs" which just holds all tarballs in a directory of
their own (or possibly subtree merging) and "release" which basically
just holds the sum total of the two branches. Having two branches with
separate starting points work just fine in git, so that shouldn't be a
problem.

OTOH, if both projects are stored in git, "release" might just as well
be a merge of master and a subtree merge of N::P.

-- 
Andreas Ericsson                   andreas.ericsson at op5.se
OP5 AB                             www.op5.se
Tel: +46 8-230225                  Fax: +46 8-230231

Considering the successes of the wars on alcohol, poverty, drugs and
terror, I think we should give some serious thought to declaring war
on peace.




More information about the Devel mailing list