On Sat, Jul 18, 2015 at 12:39:16AM +0100, Stuart Henderson wrote:
> On 2015/07/18 00:45, Christian Weisgerber wrote:
> > The attached large diff updates devel/gettext to 0.19.5.1 and, more
> > importantly, splits it into two packages:
> > 
> > gettext-runtime-0.19.5.1  GNU gettext runtime libraries and programs
> > gettext-tools-0.19.5.1    GNU gettext development and translation tools
> > 
> > This is recommended and documented by upstream.  Most users of
> > gettext only require the small runtime components.
> > 
> > -rw-r--r--  3 naddy  naddy   229K Jul 18 00:08 gettext-runtime-0.19.5.1.tgz
> > -rw-r--r--  3 naddy  naddy   5.2M Jul 18 00:08 gettext-tools-0.19.5.1.tgz
> > 
> > (It's much worse on static archs. The 5.7/vax gettext package is
> > 33.3M in size, nearly all of it tools.)
> > 
> > I don't expect anybody will read through the PLIST reorganization, but
> > the other changes could use some review, in particular the multi-package
> > details (conflict/pkgpath markings).  I think pkg_add updates work.
> 
> I like this a lot, I've had a quick look over the PLISTs and they
> seem sane, the multi-package details are fine.
> 
> > To do:
> > 
> > I will try to identify all ports that require gettext-tools for
> > building (e.g. msgfmt) and add a corresponding dependency.  Do we
> > want something like MODGETTEXT_TOOLS=Yes or explicitly add
> > BUILD_DEPENDS=devel/gettext,-tools where required?
> 
> I like MODGETTEXT_TOOLS for this.

I would have kept a BUILD_DEPENDS more, but I'm okay with MODGETTEXT_TOOLS
as well. Make sure it gets documented

Reply via email to