Date: Thu, 13 Feb 2020 15:20:56 +0100 From: Stefan Bethke <stb@lassitu.de> To: Marcin Cieslak <saper@saper.info> Cc: FreeBSD Ports <freebsd-ports@freebsd.org> Subject: Re: Debugging build with gmake, running npm toolchain Message-ID: <BA2E8A18-0518-4525-9E0B-6CACE449A4DF@lassitu.de> In-Reply-To: <nycvar.OFS.7.76.44444.807.2002131335480.61731@z.fncre.vasb> References: <777440C7-7E56-4DEA-A2EE-2550EBDC3706@lassitu.de> <nycvar.OFS.7.76.44444.807.2002131335480.61731@z.fncre.vasb>
next in thread | previous in thread | raw e-mail | index | archive | help
> Am 13.02.2020 um 14:42 schrieb Marcin Cieslak <saper@saper.info>: >=20 > On Wed, 12 Feb 2020, Stefan Bethke wrote: >=20 >> The second issue is that npm install is invoked, which will most = likely prevent the port to be built as a package. Is there a way to = handle the download of the package-lock.json dependencies in the fetch = stage? >=20 > I have some hack in my private node-sass port: = https://github.com/saper/ports-exp/tree/master/textproc/node-sass >=20 > jrm@ has solved this in the late net-im/mastodon port by simply = putting all JavaScript together > in one tarball: = https://svnweb.freebsd.org/ports/head/net-im/mastodon/?pathrev=3D472547 >=20 > https://ftfl.ca/blog/2017-05-23-mastodon-freebsd.html >=20 > The port got removed in = https://svnweb.freebsd.org/ports?view=3Drevision&revision=3D474751 = <https://svnweb.freebsd.org/ports?view=3Drevision&revision=3D474751>; Thanks for the pointers! I'm currently trying to convince upstream to package the dependencies as = vendor-like archives (for both Go modules and npms) and deploy them = alongside the source release archive. That would allow me to treat these = as additional distfiles, and simply unpack them into $WRKSRC. I'm hoping that this would make the maintenance of the port halfway = reasonable. Stefan --=20 Stefan Bethke <stb@lassitu.de> Fon +49 151 14070811
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?BA2E8A18-0518-4525-9E0B-6CACE449A4DF>