From owner-freebsd-ports@freebsd.org Mon Oct 28 12:34:25 2019 Return-Path: Delivered-To: freebsd-ports@mailman.nyi.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.nyi.freebsd.org (Postfix) with ESMTP id 9D2C11A19D3 for ; Mon, 28 Oct 2019 12:34:25 +0000 (UTC) (envelope-from wjw@digiware.nl) Received: from mailman.nyi.freebsd.org (mailman.nyi.freebsd.org [IPv6:2610:1c1:1:606c::50:13]) by mx1.freebsd.org (Postfix) with ESMTP id 471vKs1wTCz3PH1 for ; Mon, 28 Oct 2019 12:34:25 +0000 (UTC) (envelope-from wjw@digiware.nl) Received: by mailman.nyi.freebsd.org (Postfix) id 41DFD1A19D2; Mon, 28 Oct 2019 12:34:25 +0000 (UTC) Delivered-To: ports@mailman.nyi.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.nyi.freebsd.org (Postfix) with ESMTP id 41A6E1A19D1 for ; Mon, 28 Oct 2019 12:34:25 +0000 (UTC) (envelope-from wjw@digiware.nl) Received: from smtp.digiware.nl (smtp.digiware.nl [176.74.240.9]) (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 471vKr2R34z3PGy for ; Mon, 28 Oct 2019 12:34:24 +0000 (UTC) (envelope-from wjw@digiware.nl) Received: from router.digiware.nl (localhost.digiware.nl [127.0.0.1]) by smtp.digiware.nl (Postfix) with ESMTP id 26CCF32644; Mon, 28 Oct 2019 13:34:21 +0100 (CET) X-Virus-Scanned: amavisd-new at digiware.com Received: from smtp.digiware.nl ([127.0.0.1]) by router.digiware.nl (router.digiware.nl [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id OJKVjlFd8e-o; Mon, 28 Oct 2019 13:34:20 +0100 (CET) Received: from [192.168.101.70] (unknown [192.168.101.70]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by smtp.digiware.nl (Postfix) with ESMTPSA id 623C432643; Mon, 28 Oct 2019 13:34:20 +0100 (CET) Subject: Re: packaging a port that uses npm during build. To: Adam Weinberger Cc: "ports@freebsd.org" References: From: Willem Jan Withagen Message-ID: <4f4ba55b-fc5e-f700-2d78-e0c210453d4d@digiware.nl> Date: Mon, 28 Oct 2019 13:34:20 +0100 User-Agent: Mozilla/5.0 (Windows NT 10.0; WOW64; rv:60.0) Gecko/20100101 Thunderbird/60.9.0 MIME-Version: 1.0 In-Reply-To: Content-Type: text/plain; charset=utf-8; format=flowed Content-Language: en-US Content-Transfer-Encoding: 7bit X-Rspamd-Queue-Id: 471vKr2R34z3PGy X-Spamd-Bar: ----- Authentication-Results: mx1.freebsd.org; dkim=none; dmarc=none; spf=pass (mx1.freebsd.org: domain of wjw@digiware.nl designates 176.74.240.9 as permitted sender) smtp.mailfrom=wjw@digiware.nl X-Spamd-Result: default: False [-5.54 / 15.00]; ARC_NA(0.00)[]; TO_DN_EQ_ADDR_SOME(0.00)[]; RCVD_VIA_SMTP_AUTH(0.00)[]; FROM_HAS_DN(0.00)[]; TO_DN_SOME(0.00)[]; R_SPF_ALLOW(-0.20)[+mx]; NEURAL_HAM_LONG(-1.00)[-1.000,0]; MIME_GOOD(-0.10)[text/plain]; RCVD_TLS_LAST(0.00)[]; DMARC_NA(0.00)[digiware.nl]; RCVD_COUNT_THREE(0.00)[4]; TO_MATCH_ENVRCPT_SOME(0.00)[]; RCVD_IN_DNSWL_MED(-0.20)[9.240.74.176.list.dnswl.org : 127.0.9.2]; RCPT_COUNT_TWO(0.00)[2]; NEURAL_HAM_MEDIUM(-1.00)[-1.000,0]; IP_SCORE(-3.04)[ip: (-9.78), ipnet: 176.74.224.0/19(-4.89), asn: 28878(-0.54), country: NL(0.02)]; FROM_EQ_ENVFROM(0.00)[]; R_DKIM_NA(0.00)[]; MIME_TRACE(0.00)[0:+]; ASN(0.00)[asn:28878, ipnet:176.74.224.0/19, country:NL]; MID_RHS_MATCH_FROM(0.00)[] X-BeenThere: freebsd-ports@freebsd.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: Porting software to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 28 Oct 2019 12:34:25 -0000 On 28-10-2019 13:28, Adam Weinberger wrote: > On Mon, Oct 28, 2019 at 5:17 AM Willem Jan Withagen wrote: >> >> Hi, >> >> The ceph ports should have a manager module called dashboard that >> exists of a large bundle op JS-scripts that get installed with npm/node >> during running make on the configured build. >> >> Uptil now I've exclude that from builds, but that gets more and more >> complicated. Ceph cluster status is not reported not healty if the >> dashboard is not running.... >> >> Apart from the fact that npm does not like to be ran as 'root', >> poudriere also complains about fetching data afte the fetch fase. >> >> There are about 1000 npm-modules included in this project. >> So that would be a large set of things to maintain correctly. >> >> Is there a way around this? >> Or does anybody here have experience with this? >> >> I think I read once somewhere that there is also a "flag" that indicates >> that the port wants network access during the build. Is that feasible? > > Can the modules be installed after installation? As in, does a > package.json get installed somewhere? If so, I'd put the `npm install` > instructions in pkg-message. I'd have to dig deeper, but as far as I can now see it is a rather convoluted part of the Cmake infra that gets called by gmake to run several scripts and others... But the hint is very temping if it was only like: call npm in something like /usr/local/share/ceph/dasboard/frontend > The flag you're talking about has to go in poudriere.conf, so it > wouldn't be able to help much here. It's for local control. Bummer... What is the latest moment a (Make)script can get access to the network? Tried finding this in the porters manual, but could not find that detail. --WjW