Update on porting mono 5

David Naylor naylor.b.david at gmail.com
Tue Sep 5 19:10:12 UTC 2017


On Saturday, 2 September 2017 11:55:15 Robert Alegrid wrote:
> I apologize in advance if I formatted this message incorrectly or addressed
> it incorrectly. This is the first time I'm posting to a mailing list, so I
> have no real idea how I should be doing it.

Looks good to me :-), welcome to the list.  

> I also just program as a hobby (and mostly on Windows at that), so that
> should be taken in consideration as well.
> 
> On Saturday, 2 September 2017 7:03 PM, Romain Tartière wrote:
> >On Fri, Aug 25, 2017 at 09:41:43PM +0200, David Naylor wrote:
> >> [2] A general discussion needs to be had around nuget packages.  How do
> >> we
> >> consume them?
> >>
> >>   i) as downloads with each port containing a copy
> >>  ii) local ports with consistency across the Ports Collections
> >>
> >> iii) A mixture of the above (i.e. (ii) is there is a native component,
> >> otherwise (i))
> >> I prefer (ii) as I think it gives the end user the best leverage to patch
> >> issues with nuget packages locally (and to get updates without waiting on
> >> a) upstream, and b) us/ports maintainer).  However, at this point that
> >> option is at 0% progress.
> 
> It's possible for NuGet to use a local directory as a feed:
>   https://docs.microsoft.com/en-us/nuget/hosting-packages/local-feeds
> If you add the local feed earlier in the list of sources, it should pick up
> your locally built packages instead of fetching it from the internet.

Good to know, but this will still require patching each port to use a local 
feed.

> NuGet also maintains a cache of packages that it uses to restore from when
> it doesn't have an internet connection to work with.

I believe this location is $PACKAGES=$HOME/.nuget/packages and is the best 
approach to provide packages during build phase.  

Regards
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 963 bytes
Desc: This is a digitally signed message part.
URL: <http://lists.freebsd.org/pipermail/freebsd-mono/attachments/20170905/93ebc319/attachment.sig>


More information about the freebsd-mono mailing list