[Mono-devel-list] corlib runtime versioning

Ben Maurer 05mauben at hawken.edu
Fri Jan 23 12:57:29 EST 2004

I don't really understand why you say we cant do it. The way someone
should install a new build is:

1) install the new corlib
2) install the new mono

So, when we are at stage 2, the *new* mono should return a `0' when
doing the version check. This process can be done with `make fullbuild'.

Also, we could allow someone to run:
make install SANITY_CHECKS=false

to override the safeguard in non-standard cases.

The reason why I support having it in the build is that often people
will install the runtime first before building corlib. This puts them in
a really hard position, as they are not able to get out of it without
the assistance of a monocharge.

>>> Paolo Molaro <lupus at ximian.com> 01/23/04 11:26 AM >>>
On 01/22/04 Ben Maurer wrote:
> One thought I have had is that we should have the following in the
> system:
> Right before mono is about to install itself, it should execute:
> mono --check-version (where mono is the mono that was just built)
> This will return `1' if the version is too old or too new (with a
> message, etc) or `0' if all is well.

I changed mono so that "mono --verbose --version" will check if the
corlib will match, print the error and exit with a non-zero value.
We can't put the check into the install process, though, since that
would prevent the installation of new versions of mono.


lupus at debian.org                                     debian/rules
lupus at ximian.com                             Monkeys do it better
Mono-devel-list mailing list
Mono-devel-list at lists.ximian.com

More information about the Mono-devel-list mailing list