[Vm-dev] VM_VERSION triplet

[Eliot Miranda]

Hi David,

On Fri, Nov 20, 2020 at 7:00 AM stes at PANDORA.BE <stes at telenet.be> wrote:

>
> -----BEGIN PGP SIGNED MESSAGE-----
> Hash: SHA256
>
>
> An interesting side-effect of David Lewis's update of the subversion repo,
> was that I observed that the new VM is called :
>
> 4.19.2-3790    and      4.19.2-3790_64bit
>
> The subversion source code seems to be generated from the VMMaker 4.19.2,
> and this automatically sets VM_VERSION to 4.19.2 :
>
> The code in the configure script that is doing this:
>
> vmmversion="`tr '\015 ' '\012\012' < \"${interp_h}\" | sed
> '1,/VMMaker/d;q'`"
>
> VM_VERSION="${vmmversion}-${svnversion}${RELEASE_TAG}"
>
> So it automatically creates a 3 digit version with the subversion 3790
> suffix,
> based on the SVN version and the VMMaker version.
>
> The subversion version number is 3790 so far is clear, but the VM version
> seems to be set by the above code now to "4.19.2".
>
> For the Solaris IPS COMPONENT_VERSION I had a number 4.16.7
> and I updated it to the new COMPONENT_VERSION= 4.19.2 .
>
> For the squeak-5 Git OpenSmalltalk VM I would also like to use a 3 digit
> version number that makes some sense.
>
> Currently I create 3 digit numbers myself (without any relationship to
> squeak).
>
> However I was thinking that maybe I can use:
>
>    5.0.x  where x is the VMMaker version number.
>
> It appears that nowadays the VMmaker is called VMMaker.oscog-eem.2887
>
> So I could use the number 2887 in 5.0.2887 where 2887 is the VMMaker
> number.
>
> This relates to my question a few months ago as to the #define
>
> platforms/Cross/vm/sqVirtualMachine.h:# define VM_VERSION "5.0"
>
> which in my understanding sets the VM_VERSION of all  VM's to "5.0".
>
> An issue could be that the "stack" VM and the "cog" VM actually seem to
> use,
> different VMmaker numbers.
>
> For example currently for the "stack" VM the VMmaker number is 2885.
>
> For the "cog" VM the VMmaker number is 2891.
>

That's right.  The sources are generated from a particular version of
VMMaker and not all sources change.  So if I make a change that only
affects the Cog VM's interpreter the StackInterperteer VMs will not get
generated.  The situation is more varied in src/plugins.  Look at the range
of version numbers in there and you'll see a broad spread.  We don't want
to regenerate code every time if it doesn't change.

>
> So they are slightly different.
>
> I guess that what I wonder is whether it makes sense to use version
> numbers,
>
>         5.0.x
>         5.0.2885
>         5.0.2891
>
> where x= VMmaker release number following Eliot Miranda's VMmaker release.
>

Well, that would be nice.  But the effort of incrementing the version
number is very hard.  I prefer to leave it as vm -version providing the
full verison info, the VMMaker versions for interpreter and cogit (and for
all plugins), and the git commit for opensmalltalk-vm.  The basic version
number could be incremented if the build system did it automatically but I
would forget all the time.


> Is there an established triplet 3digit release number for OpenSmalltalk ??
>

No.

>
> Regards,
> David Stes
>
> -----BEGIN PGP SIGNATURE-----
> Version: GnuPG v2
>
> iQEcBAEBCAAGBQJft9m+AAoJEAwpOKXMq1MaNnEIALdzkb00VEQ/XHn+F/8G37tE
> EteNRCQtIawigsUn+aSh+OLX0NbTOyyzCbHh2ihqWFMyIvdisT9SP9FlRUzXryBR
> gW14p3xgHoLot2sGChXDro6ZLYsaRVDsnJVuzFTBuyClwlK4HwJXvJdOsEP3TMo4
> Nr8w0ldX4hDpoNvil0d/K/uxJ8Cg1XENQ4ECv0DEUv3qMgJeOynDyqRbOWRqym9e
> Gc+Bya71kKYrWLHI7/ekxO0I99p6YGYXMb+sjxM+xCY9IIxm0Lcq5IjLNEPwvvpX
> nHp1U4n9BUYc40P+Cja9m2+olI0uTix/+FzmGM3G/biqbIIf3u+B5qg97gr3z5g=
> =eFQV
> -----END PGP SIGNATURE-----
>


-- 
_,,,^..^,,,_
best, Eliot
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.squeakfoundation.org/pipermail/vm-dev/attachments/20201120/c028c376/attachment.html>