Skip site navigation (1)Skip section navigation (2)
Date:      Thu, 8 Feb 2024 22:44:17 +0100
From:      Luca Pizzamiglio <pizzamig@freebsd.org>
To:        FreeBSD Ports mailing list <freebsd-ports@freebsd.org>, ports-developers@freebsd.org
Subject:   Subpackages: Update
Message-ID:  <CAB88xy8o_d99cndg%2BnTi9fK6XfS%2Bym=Njor4%2BcVAkTqV49tfhQ@mail.gmail.com>

next in thread | raw e-mail | index | archive | help
--0000000000008ac1360610e5b7bc
Content-Type: text/plain; charset="UTF-8"

Hi FreeBSD porters.

Here are some updates about subpackages.

At the moment, subpackages adoption is *on hold*, as a few annoying issues
have been identified and they need some time to be fixed.
A bug about optional dependencies for subpackages has already been fixed
<https://cgit.freebsd.org/ports/commit/Mk?id=064923481f420136c46895d1047344c580be3c25>;
(OPT_*_DEPENDS.subpkg was not detected correctly)

The main blockers are:
* `make describe` is not subpackages aware. A fix is in review, but not yet
ready to land. This is also breaking INDEX.
* `make install` doesn't allow for partial installation. A patch is ready
and in review (https://reviews.freebsd.org/D43789) to address it (in
reference to previous email threads)
* poudriere forces the rebuild of subpackages dependency. A PR is open and
we hope to find a solution soon.
Additionally, `USES.subpkg` doesn't work properly at the moment:
dependencies (LIB and RUN) are linked to the main package, instead of the
subpackage.

Because of those issues, some subpackage commits have also been *reverted*,
waiting for the fixes to land, before being committed back.

If you are thinking of adopting subpackages, *please wait* until things get
fixed.
Once those fixes are out and the situation gets more stable, we will focus
on the *documentation*.

Best regards,
pizzamig (on behalf of portmgr)

--0000000000008ac1360610e5b7bc
Content-Type: text/html; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable

<div dir=3D"ltr"><div>Hi FreeBSD porters.</div><div><br></div><div>Here are=
 some updates about subpackages.<br></div><div><br></div><div>At the moment=
, subpackages adoption is <b>on hold</b>, as a few annoying issues have bee=
n identified and they need some time to be fixed.</div><div>A bug about opt=
ional dependencies for subpackages has already been <a href=3D"https://cgit=
.freebsd.org/ports/commit/Mk?id=3D064923481f420136c46895d1047344c580be3c25"=
>fixed</a> (OPT_*_DEPENDS.subpkg was not detected correctly)<br></div><div>=
<br></div><div>The main blockers are:</div><div>* `make describe` is not su=
bpackages aware. A fix is in review, but not yet ready to land. This is als=
o breaking INDEX.<br></div><div>* `make install` doesn&#39;t allow for part=
ial installation. A patch is ready and in review (<a href=3D"https://review=
s.freebsd.org/D43789">https://reviews.freebsd.org/D43789</a>) to address it=
 (in reference to previous email threads)<br></div><div>* poudriere forces =
the rebuild of subpackages dependency. A PR is open and we hope to find a s=
olution soon.<br></div><div>Additionally, `USES.subpkg` doesn&#39;t work pr=
operly at the moment: dependencies (LIB and RUN) are linked to the main pac=
kage, instead of the subpackage.</div><div><br></div><div>Because of those =
issues, some subpackage commits have also been <b>reverted</b>, waiting for=
 the fixes to land, before being committed back.<br></div><div><br></div><d=
iv>If you are thinking of adopting subpackages, <b>please wait</b> until th=
ings get fixed.<br></div><div>Once those fixes are out and the situation ge=
ts more stable, we will focus on the <b>documentation</b>.<br></div><br><di=
v>Best regards,</div><div>pizzamig (on behalf of portmgr)<br></div></div>

--0000000000008ac1360610e5b7bc--



Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?CAB88xy8o_d99cndg%2BnTi9fK6XfS%2Bym=Njor4%2BcVAkTqV49tfhQ>