From nobody Tue May 3 16:23:26 2022 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 8D1911ABA652 for ; Tue, 3 May 2022 20:58:43 +0000 (UTC) (envelope-from pz-freebsd-ports@ziemba.us) Received: from osmtp.ziemba.us (tc-v.ziemba.us [149.28.207.195]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (4096 bits) server-digest SHA256) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 4KtC415WPkz4rCp for ; Tue, 3 May 2022 20:58:41 +0000 (UTC) (envelope-from pz-freebsd-ports@ziemba.us) Received: from hairball.ziemba.us (localhost.ziemba.us [127.0.0.1]) by hairball.ziemba.us (8.15.2/8.15.2) with ESMTP id 243GNQMe049187 for ; Tue, 3 May 2022 09:23:26 -0700 (PDT) (envelope-from pz-freebsd-ports@ziemba.us) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=ziemba.us; s=hairball; t=1651595006; bh=jVaCDSyRXtYzz/U/JmaQmmA80T9IvxdCFzCpw1zHyb0=; h=From:To:Subject:Date:Reply-to; b=NIML6/BuyDaIjo9upE/II+DNlm2GVYOLAjtBlCMwlFxNtF/0ZixAf/YXTQ+UXG1S0 k2NHw2r0XMQomAF6omnh3aozzX/CDtvrCOH/dEjRGTEHMowQOMDsNpiNU6TqbLjJff jQXXT95Wam9fmsfOWp4LmTd7v6eH+ZI/Ycxe8cC9WCuliECUjW8LlmNnl6Kn/oGrxy Tov/cX5pFM2untB0JZ1Nj3u+3yd8bwQFPHW9x2MwPwYouDj9SofGB43w/jI+PKAYfz IUZsbKgSqDA7JZR0GE/JoH80i2auCaMi6Ynkdqo3daqPvcFM9/cfwmcU6YXKC3j5P7 UKIj4rKYTzNlw== X-Authentication-Warning: hairball.ziemba.us: Host localhost.ziemba.us [127.0.0.1] claimed to be hairball.ziemba.us Received: (from mailnull@localhost) by hairball.ziemba.us (8.15.2/8.15.2/Submit) id 243GNQdr049186 for freebsd-ports@freebsd.org; Tue, 3 May 2022 09:23:26 -0700 (PDT) (envelope-from pz-freebsd-ports@ziemba.us) X-Authentication-Warning: hairball.ziemba.us: mailnull set sender to pz-freebsd-ports@ziemba.us using -f Received: (from news@localhost) by usenet.ziemba.us (8.14.5/8.14.5/Submit) id 243GNQcb019110 for treehouse-mail-freebsd-ports@hairball.ziemba.us; Tue, 3 May 2022 09:23:26 -0700 (PDT) (envelope-from news) From: "G. Paul Ziemba" To: freebsd-ports@freebsd.org Subject: avoiding "install" for dependencies with PORTS_MODULES Date: Tue, 3 May 2022 16:23:26 +0000 (UTC) Message-id: Reply-to: unp@ziemba.us Errors-to: "G. Paul Ziemba" X-Rspamd-Queue-Id: 4KtC415WPkz4rCp X-Spamd-Bar: --- Authentication-Results: mx1.freebsd.org; dkim=pass header.d=ziemba.us header.s=hairball header.b="NIML6/Bu"; dmarc=none; spf=pass (mx1.freebsd.org: domain of pz-freebsd-ports@ziemba.us designates 149.28.207.195 as permitted sender) smtp.mailfrom=pz-freebsd-ports@ziemba.us X-Spamd-Result: default: False [-3.38 / 15.00]; HAS_REPLYTO(0.00)[unp@ziemba.us]; ARC_NA(0.00)[]; R_DKIM_ALLOW(-0.20)[ziemba.us:s=hairball]; NEURAL_HAM_MEDIUM(-1.00)[-1.000]; FROM_HAS_DN(0.00)[]; TO_MATCH_ENVRCPT_ALL(0.00)[]; R_SPF_ALLOW(-0.20)[+ip4:149.28.207.195]; MIME_GOOD(-0.10)[text/plain]; HAS_XAW(0.00)[]; REPLYTO_DOM_EQ_FROM_DOM(0.00)[]; RCPT_COUNT_ONE(0.00)[1]; NEURAL_HAM_LONG(-1.00)[-1.000]; PREVIOUSLY_DELIVERED(0.00)[freebsd-ports@freebsd.org]; MID_RHS_MATCH_FROMTLD(0.00)[]; DKIM_TRACE(0.00)[ziemba.us:+]; NEURAL_HAM_SHORT(-0.88)[-0.875]; TO_DN_NONE(0.00)[]; MLMMJ_DEST(0.00)[freebsd-ports]; DMARC_NA(0.00)[ziemba.us]; FROM_EQ_ENVFROM(0.00)[]; MIME_TRACE(0.00)[0:+]; RCVD_TLS_LAST(0.00)[]; ASN(0.00)[asn:20473, ipnet:149.28.192.0/19, country:US]; RCVD_COUNT_TWO(0.00)[2] X-ThisMailContainsUnwantedMimeParts: N 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 An unfortunate property of building ports locally (as opposed to via poudriere) is that dependencies are often installed to the host file system during the build even when I am not doing "make install" to the target port. I normally sidestep this issue by using poudriere. However, I am trying to use PORTS_MODULES in conjunction with my kernel upgrade process to generate ports-based kernel modules matching the new kernel, to avoid the "disable kmods/reboot/build ports/reenable kmods" dance. It seems "make buildkernel" uses tool binaries from a prior "make buildworld". Is it possible to, in a like manner, cause the ports built via PORTS_MODULES to install and use their dependencies in this same "world" staging tree (or in some alternate place) instead of directly in the host's file system? -- G. Paul Ziemba FreeBSD unix: 9:21AM up 130 days, 17:23, 15 users, load averages: 0.33, 0.35, 0.35