Suppose modules used git SHA1 numbers as versions. Now I want to install Module X. Module X needs module Y, and at least version 81AC89FE38.... I have version DA21348FF0... installed. Quick, do I need to update module Y to be able to use module X or not?
Exactly the point. The concept of a version number and a file identification should be separate concepts.
As analogy git has separated the concept of a file name and the file contents. The file contents is a blob which has an id. The id is then related to a name in the tree object. They are two separate concepts. The concept of version number, more like a git tag, identifies a group of items, a hash uniquely identifies the contents of something, in the case we are discussing, files as related to modules and packages in perl.
...yours is the most insane. By a long shot.
Thank you - either i'm insane or cutting new trails :)
In reply to Re^2: <pkg>::VERSION, git, hashes, shipit, Class::MOP, Moose, perl core support - what NOW makes sense.
by otto
in thread <pkg>::VERSION, git, hashes, shipit, Class::MOP, Moose, perl core support - what NOW makes sense.
by otto
| For: | Use: | ||
| & | & | ||
| < | < | ||
| > | > | ||
| [ | [ | ||
| ] | ] |