On Wed, 28 Mar 2001, Kayvan A. Sylvan wrote:
> On Thu, Mar 29, 2001 at 05:18:31PM +1000, Allan Rae wrote:
> >
> > You should be able to :
> > rm -f po/POTFILES*
> > make
> >
> > to get around this unless of course there's a Makefile.am somewhere that
> > still lists these files.
>
> The above does nothing for me.
>
> My automated lyx build does a "make rpmdist" which relies on "make dist".
And if for some reason someone commits their changes in src/ from src/
then the changes to po/POTFILES will never make it into the repository.
As a result we need to ensure that we:
cd $top_srcdir
make
to get the POTFILES correctly updated before anyone commits.
To avoid this problem affecting your builds you can change your script
from:
make rpmdist
to
rm -f po/POTFILES*
make rpmdist
This can't fail because POTFILES can safely be rebuilt at any stage.
If the timestamp of the src/.../Makefile.am files change because they were
updated during a 'cvs update' then po/POTFILES* should be regenerated
automatically. If they aren't it's a bug. I've tested this many times
and it hasn't failed for me. So an alternative explanation for the
problem is that you had a conflict in the POTFILES when they were updated
and as a result a chunk which should have been removed that included the
offending file is still present and so when make runs it still tries to
access the file.
Every update I've done in the last two days (about 8) has had conflicts in
po/POTFILES.in. This is a very good arguement for removing POTFILES.in
from CVS because I won't have to keep 'rm -f po/POTFILES*'ing.
In my testing I haven't needed po/POTFILES.in in a dist to build LyX.
Someone else should verify this and then we can cull it completely.
Allan. (ARRae)
