On 6/29/16 1:24 AM, Nicolas Passerini wrote:
Hi Dale, Therry, I am working on a libgit-based git integration for
Pharo and I am facing the same problem about version numbers. So maybe
I can help you if you are working on that.
I had the same idea as Dale, using short SHAs instead of correlative
numbers, but I didn't have the time yet to got down that path.
Therry, you said that
you'll have a bunch of stuff expecting version numbers that will
stop working.
Do you already know which stuff will stop working? That would be realy
helpful.
Nicolas,
Yes. There are a number of different places in the image where the
Monticello package name is parsed. GoferVersionReference>>parseName: is
one such place and I know that Metacello has it's own parser for
Monticello package names and there are probably a few others that are
floating around in the Monticello Browser I don't know whether tools
like Kommitter/Versionner are doing their own parsing or not.
If I'm not mistaken you will probably find all the Monticello name
parsers by looking for senders of #isDigit which should result in some
fairly obvious suspects ... then we just need to figure out if we can
create a parser that will accept a hex version number and go from there ...
If we assume that the short SHA version numbers will only be used with
Pharo5.0/6.0/GemStone (platforms for which new tools have been created),
then we might be able to pull this off...
Dale
