From: Brett Gilio <brettg@posteo.net>
To: Danny Milosavljevic <dannym@scratchpost.org>
Cc: Guix-devel <guix-devel@gnu.org>
Subject: Re: Updating mono. Adding MSBuild.
Date: Fri, 29 Mar 2019 20:14:28 +0100 [thread overview]
Message-ID: <877echijcb.fsf@posteo.net> (raw)
In-Reply-To: <20190327122310.4c8155eb@scratchpost.org>
Danny Milosavljevic writes:
> Hi,
>
>> > Mono, for most distributions, seems to be bootstrapped with a prebuilt
>> > binary mono-lite. Due to this, I am unsure of how to make the first step
>> > in correctly repackaging Mono.
>>
>> Instead of adding a new binary mono-lite, can we reuse the existing
>> “mono” package to build the new Mono?
>
> +1
>
>> (I don’t know what MSBuild is and how it would help here.)
>
> MSBuild is something like Ant for .NET. (or "make", but with more XML :) )
>
> I think Brett means that MSBuild is bundled with mono.
>
> I failed to unbundle some things just to have a CVE in one of the bundled
> dependencies DAYS later. I think it's not a good idea in general to bundle
> things. (But if it's from the same vendor and team anyway they'll probably
> update their bundled copy after fixing CVEs, too)
I will try to build a newer mono against the current version we have.
Although, there is a possible issue here that needs to be
addressed. Both Mono and Chicken produce a binary called `csi`. This is
a naming conflict, and I do not know the Guix-way for resolving naming
conflicts. Most distributions renamed the Chicken csi to `chicken-csi`
and left mono to `csi`. Does Guix have namespaces for binaries we
produce? How should I proceed here?
next prev parent reply other threads:[~2019-03-29 19:14 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-03-27 3:46 Updating mono. Adding MSBuild Brett Gilio
2019-03-27 6:43 ` Ricardo Wurmus
2019-03-27 11:23 ` Danny Milosavljevic
2019-03-29 19:14 ` Brett Gilio [this message]
2019-03-29 19:18 ` Ricardo Wurmus
2019-04-01 19:19 ` Brett Gilio
2019-04-02 8:17 ` Ricardo Wurmus
2020-01-26 15:58 ` Pierre Neidhardt
2020-02-20 10:06 ` Pierre Neidhardt
2020-02-20 16:49 ` Pierre Neidhardt
2019-03-27 11:37 ` Danny Milosavljevic
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
List information: https://guix.gnu.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=877echijcb.fsf@posteo.net \
--to=brettg@posteo.net \
--cc=dannym@scratchpost.org \
--cc=guix-devel@gnu.org \
/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 public inbox
https://git.savannah.gnu.org/cgit/guix.git
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).