[Pkg-shadow-devel] out of my depth

Serge E. Hallyn serge at hallyn.com
Tue Nov 29 21:36:34 UTC 2016

Quoting Mike Frysinger (vapier at gentoo.org):
> On 18 Sep 2016 19:14, Serge E. Hallyn wrote:
> > so the *main* thing that has been causing me to give up every time
> > I've tried to do a new release has been po/*.  In particular, a
> > 'make dist' always makes po/*.gmo re-appear.  Apparently,
> > 
> > autogen.sh calls autoreconf which calls autopoint, which creates
> > m4/po.m4, which creates po/Makefile.in.in, which creates a makefile
> > which ends up calling
> > 
> >          cd $(srcdir) && rm -f $${lang}.gmo && $(GMSGFMT) -c --statistics -o t-$${lang}.gmo $${lang}.po && mv t-$${lang}.gmo $${lang}.gmo
> > 
> > etc.  The *.gmo files are binary ones, which we don't want to be
> > shipping iiuc.  So - what is an ignorant packager to do?  It seems
> > like there must be an obvious flag to add to autoreconf in autogen.sh,
> > but I can't find it.
> you want gmo files in the dist tarball the same as you want generated
> configure files.  gmo files are produced directly from the po files
> and since the po files will never change (regardless of configure
> flags and such) once the dist tarball is created, it makes sense to
> also include the gmo files.
> otherwise, you force people wanting to build shadow to also have the
> gettext package installed simply so they can run msgfmt (ugh).
> > Should the 'make dist' target be updated to rm po/*.gmo before
> > generating the tarball?
> no.  the dist tarball should have the gmo files.

Ok - thanks, I will keep the dist tarball as is (though I will add a
gpg sig this week as requested)

I'm only going to make changes to the debian package.

More information about the Pkg-shadow-devel mailing list