comment on

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.

In reply to Re^6: Professional development with Perl - how it's done? by adrianh
in thread Professional development with Perl - how it's done? by techcode

Are you posting in the right place? Check out Where do I post X? to know for sure.
Posts may use any of the Perl Monks Approved HTML tags. Currently these include the following:
<code> <a> <b> <big> <blockquote> <br /> <dd> <dl> <dt> <em> <font> <h1> <h2> <h3> <h4> <h5> <h6> <hr /> <i> <li> <nbsp> <ol> <p> <small> <strike> <strong> <sub> <sup> <table> <td> <th> <tr> <tt> <u> <ul>
Snippets of code should be wrapped in <code> tags not <pre> tags. In fact, <pre> tags should generally be avoided. If they must be used, extreme care should be taken to ensure that their contents do not have long lines (<70 chars), in order to prevent horizontal scrolling (and possible janitor intervention).
Want more info? How to link or How to display code and escape characters are good places to start.


Keep It Simple, Stupid
	PerlMonks