[Bug 262637] lang/mono6.8: Updating Mono 6 portage with a lang/mono6 port (GitHub)
Date: Fri, 18 Mar 2022 09:18:01 UTC
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=262637 Sean Champ <lab+bsd@thinkum.space> changed: What |Removed |Added ---------------------------------------------------------------------------- Attachment #232537|0 |1 is obsolete| | Attachment #232538|0 |1 is obsolete| | --- Comment #9 from Sean Champ <lab+bsd@thinkum.space> --- Created attachment 232541 --> https://bugs.freebsd.org/bugzilla/attachment.cgi?id=232541&action=edit unified diff for lang/mono6 addition and update to lang/Makefile This new lang/mono6 port uses what may be the last available mono6 release with all submodules bundled in the same distfile. The port uses Google's upstream brotli at the latest version in ports, to update the brotli used under the mono corefx external. This update is accomplished firstly with an additional distfile and scripting in post-extract, to copy a subset of the brotli source files in a compatible location under the mono corefx external. The update is lastly accomplished with an initial patch for adduing a subst flag, then some scripting in post-patch, as to update a Makefile.am. This Makefile.am would provide a list of the brotli source files for the build. For the monolite build option, the monolite distname and version have been updated to match with the updated distsrc. There are newer Mono 6 releases available at Github. However, in order to provide those via a port build in any initial port or in any subsequent updates, it may need some additional tooling both to parse a set of recursive submodule references and to add those to some place where they can be pulled into a port makefile, as static declrations for some Mono release version. The build failrues I was seeing with the source code from github may have due it being built wil only a first-level, non-recursive set of submodule distfiles. If perhaps not all of the recursive submodules in Mono would be used for every build, maybe some scripting with filemon could serve to determine what externals/submodules are actually being used, thus which ones to keep updated for a mono-git port. The port contributed here builds succesfully. It may need additional testing, for the quality of the build itself. -- You are receiving this mail because: You are the assignee for the bug.