On Sat, May 11 2019, Christian Weisgerber <[email protected]> wrote: > GNU gettext consists of two fairly distinct parts: > * gettext-runtime: Runtime libraries and programs. > * gettext-tools: Tools and documentation for developers and translators. > Upstream recommends that these are packaged separately. > > This looks like a sterling case for MULTI_PACKAGES. However, since > this would have required bumping the REVISION of a zillion ports, > at the time we decided to _exceptionally_ split gettext into two > separate ports (devel/gettext, devel/gettext-tools). > > The latest release, gettext 0.20, adds a third distinct part: > * libtextstyle: Text styling library. > > I can split that out into another separate port (devel/libtextstyle, > or maybe textproc). Or we an bite the bullet and switch to > MULTI_PACKAGES. > > Splitting gettext into separate ports imposes a small maintenance > burden: The gettext-tools build needs to be tweaked to pick up > pre-installed libintl and libtextstyle. > > Putting everything into MULTI_PACKAGES will change the @pkgpaths > and require bumping all dependent ports or bringing down the big > _SYSTEM_VERSION hammer. > > Which way do we want to go?
As discussed MULTI_PACKAGES seems appropriate for this case, also if it simplifies the relationship between gettext and gettext-tools and makes your life easier, I'm all for it. Your call regarding _SYSTEM_VERSION. -- jca | PGP : 0x1524E7EE / 5135 92C1 AD36 5293 2BDF DDCC 0DFA 74AE 1524 E7EE
