On Sun, Oct 11, 2020 at 06:03:55PM +0200, Landry Breuil wrote: > On Sun, Oct 11, 2020 at 05:03:31PM +0200, Marc Espie wrote: > > On Sun, Oct 11, 2020 at 04:53:18PM +0200, Christian Weisgerber wrote: > > > Marc Espie: > > > > > > > The new design: > > > > > > > > The idea behind "libset" is to be able to specify a "set" of wantlib > > > > that > > > > corresponds to our package, AND to just write WANTLIB wrt that libset > > > > for > > > > that specific set of libraries. > > > > > > I'm struggling to understand whether this libset records the libraries > > > a port depends on, the libraries the port provides, or both. > > > > > > Let's say--slightly simplified from reality--we have devel/gettext > > > that provides libintl and depends on iconv from converters/libiconv. > > > What would gettext's LIBSET entry look like? > > > > > > (1) LIBSET = iconv > > > (2) LIBSET = intl > > > (3) LIBSET = intl iconv > > > > > > > > I assume any user of gettext will need both iconv and intl, so > > > > LIBSET = intl iconv > > Hmm, pretty sure some consumers of gettext only have one in their > WANTLIB and not both, in that case those ones shouldnt you the libset to > avoid an extra WANTLIB ?
How about you make a full sentence with the correct words so I get what you mean ?
