Make it a separate make target. Pj.
On Wed, May 27, 2015 at 05:04:08PM +0200, Ludovic Courtès wrote: > [email protected] (Taylan Ulrich "Bay??rl??/Kammer") skribis: > > > [email protected] (Ludovic Courtès) writes: > > > >> They???re only regenerated upon ???make dist??? or ???make -C po/guix > >> update-po???, > >> I think. > >> > >> I just run ???git reset --hard??? when that happens, which is rare. > > > > Actually I get the .po file changes when I build after e.g. "git reset > > --hard && git clean -fdx", meaning essentially bring the directory to > > the state of a freshly cloned repository. I haven't tried if it also > > happens after "make clean", but it will certainly happen to those who > > clone the repository and build for the first time. > > Yes, it happens on a first clone. > > Yet I???m uncomfortable with ignoring changes to these files because we > occasionally really want to update them and to see the changes. > > So I???m not sure what can be done. Ideas? > > Ludo???. > --
