Skip site navigation (1)Skip section navigation (2)
Date:      Fri, 23 Feb 2024 09:47:31 -0500
From:      "Dan Langille" <dan@langille.org>
To:        "Luca Pizzamiglio" <pizzamig@freebsd.org>
Cc:        freebsd-ports <freebsd-ports@freebsd.org>, ports-developers@freebsd.org
Subject:   Re: Subpackages: Update
Message-ID:  <7a03f16a-6996-4a0c-ba61-526e5a335812@app.fastmail.com>
In-Reply-To:  <CAB88xy-NU44dOwAkX7gatFFGk0fRMH%2B2jMp35m5PMQG-jeFWoA@mail.gmail.com>
References:   <CAB88xy8o_d99cndg%2BnTi9fK6XfS%2Bym=Njor4%2BcVAkTqV49tfhQ@mail.gmail.com> <42ea295f-5165-4fd5-b452-82d67f53ca03@app.fastmail.com> <CAB88xy-NU44dOwAkX7gatFFGk0fRMH%2B2jMp35m5PMQG-jeFWoA@mail.gmail.com>

next in thread | previous in thread | raw e-mail | index | archive | help
--fb913873893046ee88c74fa43da8e6dd
Content-Type: text/plain

On Tue, Feb 20, 2024, at 3:24 PM, Luca Pizzamiglio wrote:
> Hi Dan.
> 
> The list of subpackages is available via `make -V SUBPACKAGES`
> Probably, the dependencies should also be split by subpackages, when this is the case. `make -V *_DEPENDS.subpkgname` provides the dependencies
> 
> I can write directly in the github issue some of those things, for reference
> 
> Best regards,
> pizzamig

Thank you.

>From what I can tell, this won't break anything on FreshPorts - rather, subpackages seem to be additional information. It also seems like FreshPorts could be easily amended to include that information. i.e. what subpackages exist for this port? What DEPENDS exist for each subpackage? Anything which can be extracted by `make -V` is easy for FreshPorts.

The parsing of packagesite.yaml by FreshPorts would not be affected - the subpackages will still point back to the origin (e.g. foo/bar): the subpacakges will just magically appear on the right FreshPorts page.

Cheers

--
  Dan Langille
  dan@langille.org


--fb913873893046ee88c74fa43da8e6dd
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 Tue, Feb 20,=
 2024, at 3:24 PM, Luca Pizzamiglio wrote:<br></div><blockquote type=3D"=
cite" id=3D"qt" style=3D""><div dir=3D"ltr"><div>Hi Dan.<br></div><div><=
br></div><div>The list of subpackages is available via `make -V SUBPACKA=
GES`<br></div><div>Probably, the dependencies should also be split by su=
bpackages, when this is the case. `make -V *_DEPENDS.subpkgname` provide=
s the dependencies<br></div><div><br></div><div>I can write directly in =
the github issue some of those things, for reference<br></div><div><br><=
/div><div>Best regards,<br></div><div>pizzamig<br></div></div></blockquo=
te><div><br></div><div>Thank you.<br></div><div><br></div><div>From what=
 I can tell, this won't break anything on FreshPorts - rather, subpackag=
es seem to be additional information. It also seems like FreshPorts coul=
d be easily amended to include that information. i.e. what subpackages e=
xist for this port? What DEPENDS exist for each subpackage? Anything whi=
ch can be extracted by `make -V` is easy for FreshPorts.<br></div><div><=
br></div><div>The parsing of&nbsp;packagesite.yaml by FreshPorts would n=
ot be affected - the subpackages will still point back to the origin (e.=
g. foo/bar): the subpacakges will just magically appear on the right Fre=
shPorts page.<br></div><div><br></div><div>Cheers</div><div><br></div><d=
iv id=3D"sig65064480"><div class=3D"signature">--<br></div><div class=3D=
"signature">&nbsp; Dan Langille<br></div><div class=3D"signature">&nbsp;=
 dan@langille.org<br></div><div class=3D"signature"><br></div></div><div=
><br></div></body></html>
--fb913873893046ee88c74fa43da8e6dd--



Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?7a03f16a-6996-4a0c-ba61-526e5a335812>