[Pkg-shadow-devel] out of my depth

[Serge E. Hallyn]

Hm, ok.  At some point in the past debuild was failing because of
mismatches in the *.gmo files, and being binary was causing some
trouble, but I'll go ahead and try that again.

thanks.

-serge

On Sun, Sep 18, 2016 at 06:40:14PM -0700, Nicolas François wrote:
> Hi Serge,
> 
> I used make distcheck,  but that will be the same wrt gmo.
> I think you should leave them in the tar ball. The intent is/was not to
> force users to have the msgfmt tool when compiling (this is not specific to
> shadow). Also the gmo are portable.
> 
> Best regards,
> -- 
> Nekral
> 
> On Sunday, September 18, 2016, Serge E. Hallyn <serge at hallyn.com> wrote:
> 
> > On Sun, Sep 18, 2016 at 07:14:02PM -0500, Serge E. Hallyn wrote:
> > > Hey guys,
> > >
> > > 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.
> > >
> > > Should the 'make dist' target be updated to rm po/*.gmo before
> > > generating the tarball?
> > >
> > > -serge
> >
> > FWIW adding
> >
> > +dist-hook:
> > +       rm -f $(distdir)/po/*.gmo
> >
> > to Makefile.am seems to work.  But is there a better way?
> >