mercurial - How to manage multiple small parts of a library with version control -


i'm new source version control, don't want make mistake in choosing wrong setup project. have kind of "library" made of many small "procedures" (they written in pseudo-language specific of third paty software). each procedure small stand alone "package" of 2/3 files (just procedure itself, documentation, , maybe 1 or 2 other sub-procedures needed main one).

so have hundreds of procedure-packages, archived in subfolders depending on area of application, , of them more complex may use others more basic.

i modify procedures pretty in stages, improve them, of course modifications break compatibility since thei involve adding/removing input/output parameters, suppose must somehow "tag" versions of each procedure if single piece of software...

so i'm wondering what's best way manage them version control (i'm using mercurial): supposed make hundreds repositories? o_o or keep in 1 big repository , tag everytime procedure revised? or maybe learn , use subrepositories?

thanks help.

simone

i can be subrepositories (or guestrepo - no updates 2013) tags

  1. each changeset in "main" repo have linked changesets repositories, i.e. when update old changeset in master, subrepos updated accordinly
  2. tags in main repository allow mark stable|functional combinations re-use

Comments

Popular posts from this blog

Magento/PHP - Get phones on all members in a customer group -

php - Bypass Geo Redirect for specific directories -

php - .htaccess mod_rewrite for dynamic url which has domain names -