On Wed, 22 Aug 2018 13:59:51 -0400, you wrote:
>* Dan Horák [2018-08-22 03:55]:
>> a nice thing on Mono is that it is fully multi-arch, supporting all
>> Fedora arches. Won't be multi-arch problem for msbuild or .NET Core?
>
>Oh. Right, that would be a problem. .NET Core upstream essentially
* Dan Horák [2018-08-22 03:55]:
> a nice thing on Mono is that it is fully multi-arch, supporting all
> Fedora arches. Won't be multi-arch problem for msbuild or .NET Core?
Oh. Right, that would be a problem. .NET Core upstream essentially
supports x86_64 only. arm-hfp, aarch64 and x86 are
On Mon, 20 Aug 2018 17:13:42 -0400
Omair Majid wrote:
> * Michael Cronenworth [2018-08-15 10:19]:
> > On 08/15/2018 08:55 AM, Florian Weimer wrote:
> > > Are you sure about that? Ocaml does it as well.
> >
> > The guidelines allow an initial bootstrap from binaries, but
> > subsequent builds
On Fri, 17 Aug 2018 at 19:58, Richard W.M. Jones wrote:
> On Wed, Aug 15, 2018 at 03:55:26PM +0200, Florian Weimer wrote:
> > On 08/15/2018 03:20 PM, Michael Cronenworth wrote:
> > >The Roslyn compiler is now the default and requires bootstrapping
> > >from binary-only sources provided by
* Michael Cronenworth [2018-08-15 10:19]:
> On 08/15/2018 08:55 AM, Florian Weimer wrote:
> > Are you sure about that? Ocaml does it as well.
>
> The guidelines allow an initial bootstrap from binaries, but subsequent
> builds are supposed to build from source. The problem is that we can't
On Wed, Aug 15, 2018 at 03:55:26PM +0200, Florian Weimer wrote:
> On 08/15/2018 03:20 PM, Michael Cronenworth wrote:
> >The Roslyn compiler is now the default and requires bootstrapping
> >from binary-only sources provided by upstream. This is a no-no in
> >Fedora.
>
> Are you sure about that?
On Wed, Aug 15, 2018 at 03:55:26PM +0200, Florian Weimer wrote:
> On 08/15/2018 03:20 PM, Michael Cronenworth wrote:
> >The Roslyn compiler is now the default and requires bootstrapping
> >from binary-only sources provided by upstream. This is a no-no in
> >Fedora.
>
> Are you sure about that?
Hello all,
Yes, mono is behind, but it isn't a simple reason. The way mono is
bootstrapped and compiled has changed starting with version 5.0. The
Roslyn compiler is now the default and requires bootstrapping from
binary-only sources provided by upstream. This is a no-no in Fedora.
There was an
Michael Cronenworth wrote:
> On 08/15/2018 08:55 AM, Florian Weimer wrote:
>> Are you sure about that? Ocaml does it as well.
>>
>> Thanks,
>> Florian
>
> The guidelines allow an initial bootstrap from binaries, but subsequent
> builds are supposed to build from source. The problem is that we
Michael Cronenworth writes:
> On 08/15/2018 05:16 AM, Radka Janekova wrote:
>>
>> mono-devel packages are far behind upstream, and the mono-sig seems
>> unresponsive as whole. This leads me to a question, do we have a
>> maintainer for mono?
>>
>> I can
On 08/15/2018 08:55 AM, Florian Weimer wrote:
Are you sure about that? Ocaml does it as well.
Thanks,
Florian
The guidelines allow an initial bootstrap from binaries, but subsequent builds are
supposed to build from source. The problem is that we can't build without the
binaries at all.
On 15.8.2018 15:55, Florian Weimer wrote:
On 08/15/2018 03:20 PM, Michael Cronenworth wrote:
The Roslyn compiler is now the default and requires bootstrapping from
binary-only sources provided by upstream. This is a no-no in Fedora.
Are you sure about that? Ocaml does it as well.
See also:
On 08/15/2018 03:20 PM, Michael Cronenworth wrote:
The Roslyn compiler is now the default and requires bootstrapping from
binary-only sources provided by upstream. This is a no-no in Fedora.
Are you sure about that? Ocaml does it as well.
Thanks,
Florian
On 08/15/2018 05:16 AM, Radka Janekova wrote:
mono-devel packages are far behind upstream, and the mono-sig seems unresponsive
as whole. This leads me to a question, do we have a maintainer for mono?
I can take a look at it within the next month or two if there really isn't anyone
else
Hello All!
2018-08-15 12:16 GMT+02:00 Radka Janekova :
>
> Hi,
>
> mono-devel packages are far behind upstream, and the mono-sig seems
> unresponsive as whole. This leads me to a question, do we have a maintainer
> for mono?
>
> I can take a look at it with
.
On Wed, Aug 15, 2018 at 3:46 PM, Radka Janekova
wrote:
> Hi,
>
> mono-devel packages are far behind upstream, and the mono-sig seems
> unresponsive as whole. This leads me to a question, do we have a maintainer
> for mono?
>
> I can take a look at it within the next mont
Hi,
mono-devel packages are far behind upstream, and the mono-sig seems
unresponsive as whole. This leads me to a question, do we have a maintainer
for mono?
I can take a look at it within the next month or two if there really isn't
anyone else...
Regards,
Radka
17 matches
Mail list logo