Is it possible te test what the impact on the performance of opensim is
when it uses mono 2.10 or even mono 3.0 instead of mono 2.6 ?
For most linux systems it is no longer an issue to upgrade mono. In the
past it was, but time changes.
I think opensim should go for performance and not the
A minimum version of mono 2.6 does not stop people using mono 2.10 or even 3.0.
However, it allows OpenSim to work 'out-of-the-box' with older mono packages that are still shipping with some
distributions, or with long term support versions of those distros. Once people know that they want to
It seems that we are shooting for partial .net 4.0 support, and 2.6 is
where we have that. So, if we are using features found in that version,
then we are saying that version 2.6 is the bare minimum version that our
code will run on. What is wrong with that?
Mono 3 has some interesting
It's not our job to tell which version of mono people should use to run
opensim. There are way too many Linux flavors out there with different
monos, and each person running OpenSim has their own constraints and
goals. Ideally, ppl should be able to use any version of mono they
want/need.
Mono 2.10 was released Feb 15th, 2011, i.e almost two years ago. I don't
think there is any target platform that mono 2.6 runs on that doesn't have
mono 2.10 working on it as well.
There have been many bug fixes in mono between the 2.6 release and the 2.10
release, some of which can definitely
Nobody is asking you to use an older version. The minimum version is simply
the earliest version that would be required to run OpenSimulator. Anyone is
free to use any later version if they so choose.
It's also not true that later versions are necessarily better. I've
personally had to disable
If, as we both agree, OpenSim works differently with different versions of
mono then people are going to report bugs that exist when OpenSim is run on
mono versions prior to 2.10 that don't exist with mono version 2.10 and
later.
How many people are there in the OpenSim dev community that still
This page [1] seems to indicate that anyone running OpenSimulator on Debian
Squeeze (Current Stable Release) would be using* Mono v2.6.7
However, this page [2] seems to indicate that anyone running OpenSimulator
on Ubuntu 11.11 or later would be using* Mono 2.10.x
[1]
It has always been our policy to use the _lowest_ version of Mono
that we can get by on to support the largest possible number of
configurations and systems.
This is not going to change.
The feature required by recent code additions is found in Mono 2.6,
so we are discussing Mono 2.6 now. We are
That's all well and good but saying we support mono version 2.6 and
actually supporting it are two very different things.
Who here is willing to spend their time fixing problems that only appear in
versions before mono 2.10? (this isn't a rhetorical question, if you are
willing to commit to doing
Since you have already stated that you will not support older
versions, our decision will not affect you in any way.
We have, for a long time, used mono 2.4 as the base simply because
versions of distros in common use don't offer it as part of their
repo. OpenSim targets not only Windows users
We use Linux too and have downloaded and used versions of mono that were
not officially supported by the distro/version we used. There are
alternative repositories people can use that are just a Google search away.
IMO, supporting outdated mono versions is a luxury we can't afford in our
+1
On 01/24/2013 10:29 PM, Justin Clark-Casey wrote:
Whilst writing JsonStore regression tests this evening, I hit the
problem where modInvoke script methods of more than 4 parameters cannot
be registered on Mono 2.4.3 as it doesn't implement the required larger
multi-parameter Func generic
I second setting 2.10 as the base. If we'll be forcing people to upgrade I
think we should upgrade to the latest stable release and not to one that is
outdated.
If OpenSim works fine with 3.0 then I'd vote for it to be the base. If
we're still calling OpenSim alpha we should at least get the
I also second 2.10 as a base, but I think 3.0 is a bit to soon since that
version is not yet available in a lot of stable linux repo's.
On 26 jan. 2013, at 20:51, Ilan Tochner i...@kitely.com wrote:
I second setting 2.10 as the base. If we'll be forcing people to upgrade I
think we should
I think the point is raise it to the minimum version which supports the
codebase. If there was some feature in 2.10 that did not exist in 2.6 and
that feature was required for proper execution, then 2.10 would be a better
target. Otherwise it would just be forcing people to upgrade who would not
do it +1
On Thu, Jan 24, 2013 at 10:29 PM, Justin Clark-Casey
jjusti...@googlemail.com wrote:
Whilst writing JsonStore regression tests this evening, I hit the problem
where modInvoke script methods of more than 4 parameters cannot be
registered on Mono 2.4.3 as it doesn't implement the
+1
On 1/24/2013 7:29 PM, Justin Clark-Casey wrote:
Whilst writing JsonStore regression tests this evening, I hit the
problem where modInvoke script methods of more than 4 parameters
cannot be registered on Mono 2.4.3 as it doesn't implement the
required larger multi-parameter Func generic
+1
On Fri, Jan 25, 2013 at 1:57 PM, Diva Canto d...@metaverseink.com wrote:
+1
On 1/24/2013 7:29 PM, Justin Clark-Casey wrote:
Whilst writing JsonStore regression tests this evening, I hit the problem
where modInvoke script methods of more than 4 parameters cannot be
registered on Mono
Hi,
times change. Avination is 2.10.9 these days.
+1
Melanie
On 25/01/2013 23:31, Shaun Erickson wrote:
As I recall, Melanie has/had strong objections to doing this, as it would
affect her grid.
-ste
On Jan 25, 2013, at 5:20 PM, Mic Bowman cmick...@gmail.com wrote:
+1
On Fri,
Whilst writing JsonStore regression tests this evening, I hit the problem where modInvoke script methods of more than 4
parameters cannot be registered on Mono 2.4.3 as it doesn't implement the required larger multi-parameter Func generic
types.
Therefore, I want to bump the minimum Mono
21 matches
Mail list logo
