Beefy Boxes and Bandwidth Generously Provided by pair Networks
more useful options

Re: code-controlled module naming conventions?

by hobbs (Monk)
on Jul 22, 2009 at 04:26 UTC ( #782168=note: print w/replies, xml ) Need Help??

in reply to code-controlled module naming conventions?

To me, how you keep them in source control depends on how you envision them as distributions. If all of the modules are tightly coupled and you would never want to release one without another, then you would want to have

MassSpec/lib/MassSpec/ MassSpec/lib/MassSpec/ MassSpec/lib/ MassSpec/lib/LipcutElementsIO/ 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:

MassSpec-SVGIsotopeClusterGraph/lib/MassSpec/ MassSpec-SVGIsotopeClusterGraph/t/ MassSpec-SVGIsotopeClusterGraph/Makefile.PL MassSpec-ViewSpectrum/lib/MassSpec/ MassSpec-ViewSpectrum/t/ MassSpec-ViewSpectrum/Makefile.PL MassSpec-LipcutElements/MassSpec/ MassSpec-LipcutElements/MassSpec/LipcutElementsIO/ MassSpec-LipcutElements/t/ MassSpec-LipcutElements/Makefile.PL
etc. etc.

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
    Thanks to all for your responses. This one makes sense to me. My context is the "three separate components" scenario described above, as you correctly inferred.

Log In?

What's my password?
Create A New User
Domain Nodelet?
Node Status?
node history
Node Type: note [id://782168]
and the web crawler heard nothing...

How do I use this? | Other CB clients
Other Users?
Others drinking their drinks and smoking their pipes about the Monastery: (3)
As of 2022-08-15 04:17 GMT
Find Nodes?
    Voting Booth?

    No recent polls found