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?
