From nobody Fri Jun 09 18:22:12 2023 X-Original-To: freebsd-ports@mlmmj.nyi.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mlmmj.nyi.freebsd.org (Postfix) with ESMTP id 4Qd8Z865wLz4c3Hy for ; Fri, 9 Jun 2023 18:22:24 +0000 (UTC) (envelope-from hausen@punkt.de) Received: from mail.punkt.de (mail.punkt.de [217.29.41.227]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 4Qd8Z85L68z42wS; Fri, 9 Jun 2023 18:22:24 +0000 (UTC) (envelope-from hausen@punkt.de) Authentication-Results: mx1.freebsd.org; none Received: from smtpclient.apple (unknown [IPv6:2003:a:d59:3800:5928:5731:adc4:7501]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by mail.punkt.de (Postfix) with ESMTPSA id 29D336D96C; Fri, 9 Jun 2023 20:22:23 +0200 (CEST) Content-Type: text/plain; charset=utf-8 List-Id: Porting software to FreeBSD List-Archive: https://lists.freebsd.org/archives/freebsd-ports List-Help: List-Post: List-Subscribe: List-Unsubscribe: Sender: owner-freebsd-ports@freebsd.org X-BeenThere: freebsd-ports@freebsd.org Mime-Version: 1.0 (Mac OS X Mail 16.0 \(3731.600.7\)) Subject: Re: Guidance on creating a port for an npm installed tool From: "Patrick M. Hausen" In-Reply-To: <81CDD118-1475-4CF2-9180-54A8F1FEEAEF@freebsd.org> Date: Fri, 9 Jun 2023 20:22:12 +0200 Cc: Mark Millard via freebsd-ports Content-Transfer-Encoding: quoted-printable Message-Id: <8DBB6008-5EFC-4775-9FF1-7EFDA627B552@punkt.de> References: <81CDD118-1475-4CF2-9180-54A8F1FEEAEF@freebsd.org> To: Moin Rahman X-Mailer: Apple Mail (2.3731.600.7) X-Rspamd-Queue-Id: 4Qd8Z85L68z42wS X-Spamd-Bar: ---- X-Spamd-Result: default: False [-4.00 / 15.00]; REPLY(-4.00)[]; ASN(0.00)[asn:16188, ipnet:217.29.32.0/20, country:DE] X-Rspamd-Pre-Result: action=no action; module=replies; Message is reply to one we originated X-ThisMailContainsUnwantedMimeParts: N Hi, > Am 09.06.2023 um 20:15 schrieb Moin Rahman : > 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