Date: Fri, 9 Jun 2023 20:22:12 +0200 From: "Patrick M. Hausen" <hausen@punkt.de> To: Moin Rahman <bofh@FreeBSD.org> Cc: Mark Millard via freebsd-ports <freebsd-ports@freebsd.org> Subject: Re: Guidance on creating a port for an npm installed tool Message-ID: <8DBB6008-5EFC-4775-9FF1-7EFDA627B552@punkt.de> In-Reply-To: <81CDD118-1475-4CF2-9180-54A8F1FEEAEF@freebsd.org> References: <A87A6646-22EE-4371-ADC5-AA10B97AB043@punkt.de> <81CDD118-1475-4CF2-9180-54A8F1FEEAEF@freebsd.org>
next in thread | previous in thread | raw e-mail | index | archive | help
Hi, > Am 09.06.2023 um 20:15 schrieb Moin Rahman <bofh@FreeBSD.org>: > There is no specific guidelines but so far what have been most useful > is you install the package and then install the npm deps. After that > create a tarball of the npm deps installed and add it as a DISTFILE. So I create my own binary archive from the result of "npm install" or "npm run setup" or similar? That does not feel right. How will the user know that my tar archive is authentic? > One another approach is just install the dist with node as a = RUN_DEPEND > and ask user to install it through a pkg-message. Neither does this. So the state of npm based installation is that is in a mess? I'm not blaming FreeBSD or the ports system here :-) What a way to distribute software. Your second suggestion is btw out of the question because we build packages in poudriere and from these build immutable read-only base images for our jails. *sigh* Thanks for your insight. Patrick --=20 punkt.de GmbH Patrick M. Hausen .infrastructure Sophienstr. 187 76185 Karlsruhe Tel. +49 721 9109500 https://infrastructure.punkt.de info@punkt.de AG Mannheim 108285 Gesch=C3=A4ftsf=C3=BChrer: J=C3=BCrgen Egeling, Daniel Lienert, Fabian = Stein
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?8DBB6008-5EFC-4775-9FF1-7EFDA627B552>