Beefy Boxes and Bandwidth Generously Provided by pair Networks
Think about Loose Coupling
 
PerlMonks  

Re^4: Professional development with Perl - how it's done?

by adrianh (Chancellor)
on May 30, 2006 at 12:05 UTC ( [id://552475]=note: print w/replies, xml ) Need Help??


in reply to Re^3: Professional development with Perl - how it's done?
in thread Professional development with Perl - how it's done?

You have obviously not used SVN's merging tools. While very nice when they work, they often don't work, requiring a lot of hand-merging.

The wonderful SVK can help a lot there.

Frankly, it's much better just to use the CPAN shell to install the version you want to install. Most of the time, installing the latest and greatest will be good enough.

I prefer having my dependencies under source control outside of CPAN. Makes integrating them with the rest of my build much easier, and helps those occasions that aren't "most of the time" become less painful.

  • Comment on Re^4: Professional development with Perl - how it's done?

Replies are listed 'Best First'.
Re^5: Professional development with Perl - how it's done?
by dragonchild (Archbishop) on May 30, 2006 at 14:02 UTC
    I use SVK - while better than SVN,
    • that's not saying much
    • it still has issues

    Incompatible changes still have to be merged by hand. Some CPAN modules may change a couple lines a release. Then, there's modules like DBM::Deep that will add and remove whole files and those that stay will be significantly changed, even though the API and behavior that you care about hasn't changed at all.


    My criteria for good software:
    1. Does it work?
    2. Can someone else come in, make a change, and be reasonably certain no bugs were introduced?
      that's not saying much

      Well personally I think svk's merge support is significantly better than SVNs. I find the trivial handling of mirrors and remote branches/merges a joy.

      it still has issues

      Yup... I do hit snags occasionally. Very occasionally though.

      Incompatible changes still have to be merged by hand.

      True - but that's always going to be necessary.

      Some CPAN modules may change a couple lines a release. Then, there's modules like DBM::Deep that will add and remove whole files and those that stay will be significantly changed, even though the API and behavior that you care about hasn't changed at all.

      All true - and I still prefer to have all the dependencies for my build in source control so I can figure out those changes if/when they cause problems.

Log In?
Username:
Password:

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

How do I use this?Last hourOther CB clients
Other Users?
Others examining the Monastery: (7)
As of 2024-04-19 09:29 GMT
Sections?
Information?
Find Nodes?
Leftovers?
    Voting Booth?

    No recent polls found