From nobody Fri Oct 25 17:39:05 2024 X-Original-To: freebsd-pkgbase@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 4XZqmB137Yz5Zyl0 for ; Fri, 25 Oct 2024 17:39:38 +0000 (UTC) (envelope-from freebsd@wagsky.com) Received: from mx2.allycomm.com (mx2.allycomm.com [157.230.226.218]) (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 4XZqm92wbBz4SVm for ; Fri, 25 Oct 2024 17:39:37 +0000 (UTC) (envelope-from freebsd@wagsky.com) Authentication-Results: mx1.freebsd.org; dkim=pass header.d=wagsky.com header.s=default header.b=XFWZK60N; spf=pass (mx1.freebsd.org: domain of freebsd@wagsky.com designates 157.230.226.218 as permitted sender) smtp.mailfrom=freebsd@wagsky.com; dmarc=none Received: from [IPV6:2601:647:4b01:5daa:6454:fbf5:95f9:419a] (unknown [IPv6:2601:647:4b01:5daa:6454:fbf5:95f9:419a]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature ECDSA (secp384r1) server-digest SHA384) (Client did not present a certificate) by mx2.allycomm.com (Postfix) with ESMTPSA id 6F3AB1B526; Fri, 25 Oct 2024 10:39:06 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=wagsky.com; s=default; t=1729877946; bh=mIWcNsUwTeZGzvyZ3fItsnG4dIp0YUmE/05KilmRgn0=; h=Date:To:From:Subject; b=XFWZK60NlE8oV8tktI8bz7bXJdtf2T5frIkRp+vyxsjidLRQnlxpjw+mglMPLK2df GZyv/b5S5E0xjbW1dUWZizmE+G/a0hY07e+iWSUo9LtLWBafpDcxvQgRjWd3uRqlVQ f6vSd2kMmno/170D5JSRpqN9E7fntz+1MH8/tKe1lhas9nGxZDZblZXCri0pCSwS8e hfIT+/bI/0OdlUVWgBz5CTiLltVHBYcWDMbUSItSjPI0InaZeNJ3jyZUTsO9Hzt7v2 ErmV94CQLGmu1X12LCYJ+hZvi0gjqO35kNwpBXIGpqT8CHc5feSSYXckpZ3317sYoc UfIQayf2My2rw== Message-ID: Date: Fri, 25 Oct 2024 10:39:05 -0700 List-Id: Packaging the FreeBSD base system List-Archive: https://lists.freebsd.org/archives/freebsd-pkgbase List-Help: List-Post: List-Subscribe: List-Unsubscribe: Sender: owner-freebsd-pkgbase@FreeBSD.org MIME-Version: 1.0 User-Agent: Mozilla Thunderbird Content-Language: en-US To: freebsd-pkgbase@freebsd.org From: Jeff Kletsky Subject: Access to package list or manifest in source? Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 7bit X-Spamd-Result: default: False [-2.39 / 15.00]; SUBJECT_ENDS_QUESTION(1.00)[]; NEURAL_HAM_LONG(-1.00)[-1.000]; NEURAL_HAM_MEDIUM(-1.00)[-1.000]; NEURAL_HAM_SHORT(-1.00)[-0.998]; R_SPF_ALLOW(-0.20)[+mx]; R_DKIM_ALLOW(-0.20)[wagsky.com:s=default]; MIME_GOOD(-0.10)[text/plain]; ONCE_RECEIVED(0.10)[]; XM_UA_NO_VERSION(0.01)[]; RCVD_VIA_SMTP_AUTH(0.00)[]; RCVD_COUNT_ONE(0.00)[1]; RCPT_COUNT_ONE(0.00)[1]; MIME_TRACE(0.00)[0:+]; ASN(0.00)[asn:14061, ipnet:157.230.224.0/20, country:US]; RCVD_TLS_ALL(0.00)[]; MID_RHS_MATCH_FROM(0.00)[]; ARC_NA(0.00)[]; FROM_EQ_ENVFROM(0.00)[]; FROM_HAS_DN(0.00)[]; DMARC_NA(0.00)[wagsky.com]; TO_DN_NONE(0.00)[]; MLMMJ_DEST(0.00)[freebsd-pkgbase@freebsd.org]; TO_MATCH_ENVRCPT_ALL(0.00)[]; DKIM_TRACE(0.00)[wagsky.com:+] X-Rspamd-Queue-Id: 4XZqm92wbBz4SVm X-Spamd-Bar: -- I'm planning on testing out pkgbase for maintaining jail file systems on the 14 RELEASE family, including the upcoming 14.1 to 14.2 transition. I looked for a reasonably clear way to determine the contents of the packages without resorting to downloading and examining them. Perhaps I was looking in the wrong place, but I did not find the equivalent of `pkg-plist` in the FreeBSD source repo. I did chase down seemingly related commits, such as 2f9966f "packages: add package for NTP" which seems to add a `PACKAGE= ntp` notation to around 20 `Makefile`s, but nothing that I saw that looks like a plist. Having a plist or manifest would help determining a nearly minimal set of base packages that are needed for each jail, especially when it comes to libraries or certain utilities that might be needed for traditional packages and their rc scripts. Is this information available without extracting from the built/downloaded packages? If it is only available as a build artifact, it might be valuable to provide it along with the packages. TIA, Jeff