[Mono-dev] Apply a patch or install unstable version? And which?

[Daniel Lo Nigro]

>
> I've answered to other question that "as GitHub already provides it
> (compressed exports) on the tags page
> (https://github.com/mono/mono/tags) it is not needed to do (source)
> releases at
> http://download.mono-project.com/sources/mono/."


Have you tried compiling these Github exports? I don't think they work as
expected, as they don't include submodules (so you need to download a bunch
of dependencies manually).


On Thu, Apr 18, 2013 at 9:45 PM, Rafael Teixeira <monoman at gmail.com> wrote:

> Hi APS,
>
> I've answered to other question that "as GitHub already provides it
> (compressed exports) on the tags page
> (https://github.com/mono/mono/tags) it is not needed to do (source)
> releases at
> http://download.mono-project.com/sources/mono/."
>
> From there you can see many tags (although some mis-versioning is present).
>
> Tags for the 3.0 series (which is installed with Xamarin Studio in
> MacOSX) are available. For example, the latest seems to be
> https://github.com/mono/mono/archive/mono-3.10.tar.gz that seems by
> its date to be the version following 3.0.9.
>
> As for stability, I guess that tagged versions should be considered
> reliable enough, but testing for what you need is the only way to be
> sure...
>
> Hope it helps,
> Rafael Teixeira
> O..:.)oooo
>
>
> On Thu, Apr 18, 2013 at 7:39 AM, APS <dev.malst at apsystems.it> wrote:
> > You're right, the patch has not been applied yet. I've to apply the
> patch to
> > my sources.
> > Btw, how mono versions works?
> > The last stable version, according to the website is 2.10.9, every other
> > versions after that is supposed to be unstable, am I right?
> > The last 2.1x version announced is 2.11.4. The 2.12 does not exists, it
> has
> > been renamed to 3.0?
> > In one of his blog posts Miguel says that the trunk is merged only with
> > working changes, so it should be less unstable than older unstable
> versions.
> > All these questions fall in the last one, for a production environment is
> > safer to install 2.10.9, the last stable but without recent patches and,
> > from today, with no more support or the 3.0.x, the beta version but fixed
> > and checked?
> > Sorry for these banal questions but I've to plan upgrades and I would
> like
> > to do the correct thing.
> >
> >
> > At 18:24 17/04/2013, Rafael Teixeira wrote:
> >>
> >> The bug is not 'Closed', so probably the patch wasn't reviewed and
> >> applied to sources, yet.
> >> Rafael Teixeira
> >> O..:.)oooo
> >>
> >>
> >> On Wed, Apr 17, 2013 at 11:43 AM, APS <dev.malst at apsystems.it> wrote:
> >> > Hi,
> >> > I have a doubt caused by my ignorance on how mono versions are
> released.
> >> > I installed the latest stable release, 2.10.9 from sources and I fell
> >> > into
> >> > the bug described here
> https://bugzilla.xamarin.com/show_bug.cgi?id=3004
> >> > I don't know if it's better for me to apply the patch to my code or to
> >> > install a later version. I saw non-documented versions like 2.11.x,
> they
> >> > are
> >> > unstable? Abandoned? Why they are not listed between the versions
> under
> >> > download page?
> >> > Thanks in advance for yout help.
> >> >
> >> > _______________________________________________
> >> > Mono-devel-list mailing list
> >> > Mono-devel-list at lists.ximian.com
> >> > http://lists.ximian.com/mailman/listinfo/mono-devel-list
> >> >
> >>
> >> --
> >> Il messaggio e' stato analizzato alla ricerca di virus o
> >> contenuti pericolosi da MailScanner, ed e'
> >> risultato non infetto.
> >
> >
> > _______________________________________________
> > Mono-devel-list mailing list
> > Mono-devel-list at lists.ximian.com
> > http://lists.ximian.com/mailman/listinfo/mono-devel-list
> _______________________________________________
> Mono-devel-list mailing list
> Mono-devel-list at lists.ximian.com
> http://lists.ximian.com/mailman/listinfo/mono-devel-list
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.ximian.com/pipermail/mono-devel-list/attachments/20130420/2a4a753a/attachment.html>