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 [email protected]
