|There's more than one way to do things|
honegrown module placementby chexmix (Hermit)
|on Jun 03, 2013 at 14:20 UTC||Need Help??|
chexmix has asked for the
wisdom of the Perl Monks concerning the following question:
Good morning, Monks:
My department is assuming management of its own Perl installation, and we're using perlbrew to simplify this. So far I have to say the setup has been pretty smooth, but I have run up against a question I'm not sure how to answer:
We have a number of home-grown modules (e.g. things that are not on CPAN and have little (well, no) reason to go there because they are so specific to the ways we do things here.
I'm not sure where in the module hierarchy such things should go. Maybe it doesn't matter as long as we are consistent?
My first impulse was to create a subdirectory under site-perl, named after our department, and put our modules in a tree beneath that subdirectory ... but maybe there is a better option.
Am I just making this more complicated than it is? ;^) It certainly wouldn't be the first time I'd done so ...