|laziness, impatience, and hubris|
Best way to manage package versions?by AlfaProject (Beadle)
|on Jan 31, 2013 at 14:36 UTC||Need Help??|
AlfaProject has asked for the
wisdom of the Perl Monks concerning the following question:
We are using Perl in our project, soon we will have few additional programmers working on a same project.
Today I'm using regular 'require' to get all other .pm files with functions.
Now I thinking how we will work with that, if other programmers will edit one of the functions file and make an error , it will crush all program.
Maybe best way to move all code to packages, and use 'use' package function to get functions I need.
The problem is how I manage versions of packages if one of the programmers want to make an update for some code in a package ?
What approaches Perl have for this situation ?
I don't want to use third party storage like git or programs that will manage it automatically.
Just searching for best logical approach for this