From: "Zhu Zihao" <all_but_last@163.com>
To: "Maxim Cournoyer" <maxim.cournoyer@gmail.com>
Cc: guix-devel <guix-devel@gnu.org>, zamfofex <zamfofex@twdb.moe>,
55026@debbugs.gnu.org
Subject: bug#55026: Re: bug#55026: potential prebuilt binaries in the Mono package
Date: Sat, 13 Aug 2022 13:34:31 +0800 (CST) [thread overview]
Message-ID: <6c881da1.ec9.18295b25f9e.Coremail.all_but_last@163.com> (raw)
In-Reply-To: <87bkspdyao.fsf@gmail.com>
[-- Attachment #1: Type: text/plain, Size: 986 bytes --]
Agree.
Actually, there's more prebuilt binaries in Mono 6 (current version)
And it's impossible to remove these binaries (see https://github.com/dotnet/source-build/issues/1930)
At 2022-08-13 04:03:43, "Maxim Cournoyer" <maxim.cournoyer@gmail.com> wrote:
>Hi,
>
>zamfofex <zamfofex@twdb.moe> writes:
>
>> It seems the package for Mono in Guix uses a tarball that contains a
>> lot of prebuilt DLLs. This doesn’t seem to have been mentioned when
>> the package was introduced. Could it have been a mistake? Some related
>> discussion: <https://github.com/mono/mono/issues/7445> and also
>> <https://logs.guix.gnu.org/guix/2022-04-19.log#195614>
>
>If nobody volunteers to do the work necessary to get our mono package to
>build without prebuilt binaries in the next 2 weeks, I suggest we remove
>it from our collection. Only a handful package depend on it, most of
>them optionally it seems, and the mono we carry is severely outdated
>(2016).
>
>What do you think?
>
>Maxim
[-- Attachment #2: Type: text/html, Size: 1263 bytes --]
next prev parent reply other threads:[~2022-08-13 5:35 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-04-19 18:19 bug#55026: potential prebuilt binaries in the Mono package zamfofex
2022-08-12 20:03 ` Maxim Cournoyer
2022-08-12 20:08 ` Maxime Devos
2022-08-13 5:34 ` Zhu Zihao [this message]
2022-09-01 23:10 ` Maxim Cournoyer
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=6c881da1.ec9.18295b25f9e.Coremail.all_but_last@163.com \
--to=all_but_last@163.com \
--cc=55026@debbugs.gnu.org \
--cc=guix-devel@gnu.org \
--cc=maxim.cournoyer@gmail.com \
--cc=zamfofex@twdb.moe \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
Code repositories for project(s) associated with this external index
https://git.savannah.gnu.org/cgit/guix.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.