Date: Mon, 12 Feb 2024 09:21:55 -0500 From: "Dan Langille" <dan@langille.org> To: "Luca Pizzamiglio" <pizzamig@freebsd.org>, freebsd-ports <freebsd-ports@freebsd.org>, ports-developers@freebsd.org Subject: Re: Subpackages: Update Message-ID: <42ea295f-5165-4fd5-b452-82d67f53ca03@app.fastmail.com> In-Reply-To: <CAB88xy8o_d99cndg%2BnTi9fK6XfS%2Bym=Njor4%2BcVAkTqV49tfhQ@mail.gmail.com> References: <CAB88xy8o_d99cndg%2BnTi9fK6XfS%2Bym=Njor4%2BcVAkTqV49tfhQ@mail.gmail.com>
next in thread | previous in thread | raw e-mail | index | archive | help
--d771095765c44e41a548d629e7796bfc Content-Type: text/plain On Thu, Feb 8, 2024, at 4:44 PM, Luca Pizzamiglio wrote: > 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*. I'm thinking about this from a FreshPorts point of view. With respect to subpackages, what will people want to see on the page for a given port? * list subpackages for this port? how do I get a list of subpackages for a port? make -V SUBPACKAGES ? * list of packages built by this port (I'm guessing packages.yaml will point back to the port) * is there any other information thought to be relevant to have on the page? re: https://github.com/FreshPorts/freshports/issues/544 -- Dan Langille dan@langille.org --d771095765c44e41a548d629e7796bfc Content-Type: text/html Content-Transfer-Encoding: quoted-printable <!DOCTYPE html><html><head><title></title><style type=3D"text/css">p.Mso= Normal,p.MsoNoSpacing{margin:0}</style></head><body><div>On Thu, Feb 8, = 2024, at 4:44 PM, Luca Pizzamiglio wrote:<br></div><blockquote type=3D"c= ite" id=3D"qt" style=3D""><div dir=3D"ltr"><div>Hi FreeBSD porters.<br><= /div><div><br></div><div>Here are some updates about subpackages.<br></d= iv><div><br></div><div>At the moment, subpackages adoption is <b>on hold= </b>, as a few annoying issues have been identified and they need some t= ime to be fixed.<br></div><div>A bug about optional dependencies for sub= packages has already been <a href=3D"https://cgit.freebsd.org/ports/comm= it/Mk?id=3D064923481f420136c46895d1047344c580be3c25">fixed</a> (OPT_*_DE= PENDS.subpkg was not detected correctly)<br></div><div><br></div><div>Th= e main blockers are:<br></div><div>* `make describe` is not subpackages = aware. A fix is in review, but not yet ready to land. This is also break= ing INDEX.<br></div><div>* `make install` doesn't allow for partial inst= allation. A patch is ready and in review (<a href=3D"https://reviews.fre= ebsd.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 solution soon.<br></div><div>Additionally, `USES.subpkg` doesn't work= properly at the moment: dependencies (LIB and RUN) are linked to the ma= in package, instead of the subpackage.<br></div><div><br></div><div>Beca= use of those issues, some subpackage commits have also been <b>reverted<= /b>, waiting for the fixes to land, before being committed back.<br></di= v><div><br></div><div>If you are thinking of adopting subpackages, <b>pl= ease wait</b> until things get fixed.<br></div><div>Once those fixes are= out and the situation gets more stable, we will focus on the <b>documen= tation</b>.<br></div></div></blockquote><div id=3D"sig65064480"><div cla= ss=3D"signature"><br></div><div class=3D"signature">I'm thinking about t= his from a FreshPorts point of view. With respect to subpackages, what w= ill people want to see on the page for a given port?<br></div><div class= =3D"signature"><br></div><div class=3D"signature">* list subpackages for= this port? how do I get a list of subpackages for a port? make -V SUBPA= CKAGES ?<br></div><div class=3D"signature">* list of packages built by t= his port (I'm guessing packages.yaml will point back to the port)<br></d= iv><div class=3D"signature">* is there any other information thought to = be relevant to have on the page?<br></div><div class=3D"signature"><br><= /div><div class=3D"signature">re: <a href=3D"https://github.com/Fre= shPorts/freshports/issues/544">https://github.com/FreshPorts/freshports/= issues/544</a></div><div class=3D"signature">--<br></div><div class=3D"s= ignature"> Dan Langille<br></div><div class=3D"signature"> d= an@langille.org<br></div><div class=3D"signature"><br></div><div><br></d= iv></div><div><br></div></body></html> --d771095765c44e41a548d629e7796bfc--
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?42ea295f-5165-4fd5-b452-82d67f53ca03>