in reply to code-controlled module naming conventions?
etc.MassSpec/lib/MassSpec/SVGIsotopeClusterGraph.pm MassSpec/lib/MassSpec/ViewSpectrum.pm MassSpec/lib/LipcutElementsIO.pm MassSpec/lib/LipcutElementsIO/Search.pm MassSpec/t/ MassSpec/Makefile.PL
If you had three separate components that could be maintained and updated separately, then you would treat them as three distributions:
etc. etc.MassSpec-SVGIsotopeClusterGraph/lib/MassSpec/SVGIsotopeclusterGraph.pm MassSpec-SVGIsotopeClusterGraph/t/ MassSpec-SVGIsotopeClusterGraph/Makefile.PL MassSpec-ViewSpectrum/lib/MassSpec/ViewSpectrum.pm MassSpec-ViewSpectrum/t/ MassSpec-ViewSpectrum/Makefile.PL MassSpec-LipcutElements/MassSpec/LipcutElementsIO.pm MassSpec-LipcutElements/MassSpec/LipcutElementsIO/Search.pm MassSpec-LipcutElements/t/ MassSpec-LipcutElements/Makefile.PL
And if all four of them are envisioned as separate components then you might have four dists, but I'm guessing it's not so, and I think I've played with <code> enough for now. ;)
|
|---|
| Replies are listed 'Best First'. | |
|---|---|
|
Re^2: code-controlled module naming conventions?
by jae_63 (Beadle) on Jul 22, 2009 at 15:43 UTC |