On 5/17/23 08:31, Stuart Henderson wrote:
> On 2023/05/17 12:36, Lee Thomas wrote:
>> Hello porters,
>>
>> I am considering creating a port for the hypercore protocol
>> (https://github.com/holepunchto) and have asked the developers for their
>> blessing.
>>
>> Reading the Porter's guide, I see it says "The most important thing to do is
>> to communicate." hence this message!
>>
>> I've got hypercore to install and pass all its tests on v7.3 amd64 with some
>> tweaks to the compilation process for its dependencies. (see issue here:
>> https://github.com/holepunchto/hypercore/issues/377).
> Looking at this, you're using npm and git to fetch things to build.
>
> A port needs to work from already downloaded distfiles i.e. without
> having network access during the build.
>
> Generally where there are already ports which have some use of npm
> in the build process (e.g. I think there are some go-based ports
> which uses npm when building the user interface), those parts using
> npm are pre-generated and the results tarred up to use in the port.
>
> But since it appears there are some native components in there
> which do need to be compiled, that pre-generated approach won't work.
>
> Not sure what to suggest, but I don't think we have a good way to
> handle this in ports.
>
Might be possible to wrangle it out with npm cache or npm pack.
