Re: Best practice for customization to allow persistance between versions?

["Chris Travers" <..hidden..>]

In general, I would suggest taking the approach of putting new
functionality in separate Perl modules at least on the .pm level.
This way you aren't manually merging this.  From an ecommerce engine,
I would recommend a separate set of scripts.  As a starting point I
wrote something before the fork.  If it is of interest I could get it
working on LSMB.  It isn;'t much yet, but could be expanded by various
community members.

I would try to keep modifications to distributed files to a minimum
currently.  The reason is that a lot of things are going to be
refactored over the next couple years so you may have to re-engineer
such changes.

Best Wishes,
Chris Travers