From nobody Fri Jan 26 16:36:47 2024 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 4TM3Hj2yvVz58RXs for ; Fri, 26 Jan 2024 16:36:49 +0000 (UTC) (envelope-from se@FreeBSD.org) Received: from smtp.freebsd.org (smtp.freebsd.org [IPv6:2610:1c1:1:606c::24b:4]) (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-signature RSA-PSS (4096 bits) client-digest SHA256) (Client CN "smtp.freebsd.org", Issuer "R3" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 4TM3Hj24wkz4kSj; Fri, 26 Jan 2024 16:36:49 +0000 (UTC) (envelope-from se@FreeBSD.org) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=freebsd.org; s=dkim; t=1706287009; h=from:from:reply-to:subject:subject:date:date:message-id:message-id: to:to:cc:cc:mime-version:mime-version:content-type:content-type: content-transfer-encoding:content-transfer-encoding: in-reply-to:in-reply-to:references:references; bh=/kSKM/QyJCVALQ6KtT7dTBfdoyLfXd8oS2Vkm5FJ/hE=; b=FO664UBDdF3VFuzywz4z7YHQcvdDAJnV4B84DIA+ADWeFxYJpLUK+7oT4M7H5bB5e0BLtm iMGd9tYQ+0HPJjAb4l3CV+y/IX8plel1L7geG4a8GEiD658FyJZNaaEkzApslc7IskQ6/h 7ykRgw11xzzLYQLnmWKwbTb4T59psZFJujuIeJkBWF+06/vBAJe1+2jBEEKrfh+gQMj5DX 1XVLWQKf8esD2QhJiIrsgHL5GMpIS5NrjXX/zeHDhNHjf3OPZqZO7YVyhiz1UG8nMWv7qj K9OPJetT1K3YdrIKGsIRl/I0WgSgRu1/qNCAmzHrH9sM76EQWzVwdN8YPtInjw== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=freebsd.org; s=dkim; t=1706287009; h=from:from:reply-to:subject:subject:date:date:message-id:message-id: to:to:cc:cc:mime-version:mime-version:content-type:content-type: content-transfer-encoding:content-transfer-encoding: in-reply-to:in-reply-to:references:references; bh=/kSKM/QyJCVALQ6KtT7dTBfdoyLfXd8oS2Vkm5FJ/hE=; b=hsRrBKS+b9Gp+Zs1YRHOgSjSVCl8Vcb1uLDEj/zILw6JJ2jQtG4j3HLH20b2oxltJuaGEf Evx01c3vCuIX+/AMw8q1s7tt6jraZfmi8nfPMMiAGRp0jlLkN9WN+mLabLziGqfchfbK0X /5cdwBp5zyUcjfBKffBizaJYvBJRM6hZBHlollZivBXKu7ZlQN5m7OzQiQp4Ek1zFvSxlu HxMeewQ/lo4H5KtNWYo+xEwsGKv5kStqfhTqGifryiWdYEC+1QiP/FT12tOFMXCyiGDLtB NDv6eZR7y8WYp8yOvPJCBve3ahFGEc+Bo+caMWquUgO1gjx2vdGWsqiZoSebnA== ARC-Authentication-Results: i=1; mx1.freebsd.org; none ARC-Seal: i=1; s=dkim; d=freebsd.org; t=1706287009; a=rsa-sha256; cv=none; b=rv9fUNHLB+Obuj5KsKxyl9C8p2XyjW5Dt4mB/ra8vDVUoC9zWy+89Vvu/++KQ8X0R721c+ E5mXeU7QrzeGtg40wwr5fMXNqfZOQVe753BED4reYKoF/IbFx19MpBALbIQeojRi6VGgEw 0ANROdwOIeQfli4ch4vcHzRzM/XdPmlQMwlT+QLzklh61hTBKKJNiLPqYU3CTOwYLScRbD kqGKhMFSrBalyUM+se+xFkAn9K2O+caRSPTEAkE4qFBGn2cXhwt4DCBTBvNWpv6Yomkj8S M9h2WMZiX/6/UQ47iwIrPRj5PWKjvFVULhTQezQNYMcLDr4L5llt5bPDdmwalg== Received: from [IPV6:2003:cd:5f2c:9d00:fc60:6ac1:1a5b:ca5] (p200300cd5f2c9d00fc606ac11a5b0ca5.dip0.t-ipconnect.de [IPv6:2003:cd:5f2c:9d00:fc60:6ac1:1a5b:ca5]) (using TLSv1.3 with cipher TLS_AES_128_GCM_SHA256 (128/128 bits) key-exchange X25519 server-signature RSA-PSS (4096 bits) server-digest SHA256) (Client did not present a certificate) (Authenticated sender: se/mail) by smtp.freebsd.org (Postfix) with ESMTPSA id 4TM3Hh563jzYP9; Fri, 26 Jan 2024 16:36:48 +0000 (UTC) (envelope-from se@FreeBSD.org) Message-ID: Date: Fri, 26 Jan 2024 17:36:47 +0100 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 User-Agent: Mozilla Thunderbird From: Stefan Esser Subject: Re: Subpackage explanations Content-Language: de-DE, en-US To: Shane Ambler References: Cc: FreeBSD Ports mailing list In-Reply-To: Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 7bit Am 25.01.24 um 04:46 schrieb Shane Ambler: > On 24/1/24 19:58, Luca Pizzamiglio wrote: >> Hi porters! >> >> At the beginning of January, we merged the support to subpackages in the >> framework. > > Sounds like some good work in the right direction. > >> *Use cases we want to tackle* >> The first use case we want to get rid of is master/slave ports when slave >> ports could be built with the master port. > > I don't see any mention of flavors. If I merge a slave port that builds > the python bindings into the master port, can I still build multiple > flavors for the subpackage? > > Any possibility that build steps can be defined to be repeated for each > desired flavor? > > do-build-flavor: > make --DPYVERS=${PY_FLAVOR} > > do-build-PY38: > make --DUSE_FUTURES=yes > > >> *Use cases we don't want to tackle (yet)* >> Subpackages enable the adoption of micro-subpackages, a typical pattern for >> Linux distributions that split a package in smaller ones: one with docs >> (-doc), one with static libraries and headers (-dev), one with manpages >> (-man), one with examples (-examples), and so on. > > To me that sounds like the easy first use case. Turn the > doc/test/example options into subpackages. Building docs often has very large dependency trees, and if docs are made subpackages, then building a port will require all these dependencies to be available, which may take orders of magnitude longer than building the port itself. The same is sometimes true for tests that have large dependencies.