On 21 January 2011 18:48, Dale Henrichs <[email protected]> wrote: > On 01/21/2011 08:11 AM, Miguel Cobá wrote: >> >> El vie, 21-01-2011 a las 11:05 +0100, Igor Stasenko escribió: >> >>> Okay, i found the solution. Use Installer ! >>> >>> Installer monticello http: 'http://www.squeaksource.com'; >>> project: 'VMMaker'; >>> install: 'CMakeVMMaker' >>> >>> >>> works well for me and loads correct *latest* version. >> >> That isn't a solution and open again a gratuitous discussion about gofer >> vs installer. >> >> The point is, in a distributed SCM system, like Monticello is, there >> isn't a latest version. At least not by the traditional (suversion for >> example) way of knowing the monotone numeric integer version number. As >> Lukas said, the only way to know something is latest is to compare >> timestamps, but not version numbers or commits id. They aren't not >> intended to be ordered respect to time. >> >> Cheers >> > > It seems to me that that isn't quite the issue ... for Metacello I had to > change the sort algorithm that Gofer used to more closely match the > algorithm used by the Monticello GUI when it sorts packages ... to minimize > the surprise for developers who are used to the Monticello GUI sorting > order... I also had to change the branch naming scheme that was used by > Gofer, because it caused problems when package names inadvertently looked > like a branch to Gofer when it wasn't...Since there has never been an > enforced naming convention in Monticello, there are a whole lot of > incompatible naming schemes being used... > > BTW, I made these changes so that they only applied to Metacello's use of > Gofer ... > good to know > Dale > >
-- Best regards, Igor Stasenko AKA sig.
