On 5 Jul 2001, Lars Gullik Bjønnes wrote:
> Allan Rae <[EMAIL PROTECTED]> writes:
>
> | On 5 Jul 2001, Jean-Marc Lasgouttes wrote:
> |
> | > >>>>> "Allan" == Allan Rae <[EMAIL PROTECTED]> writes:
> | >
> | > Allan> This still has the problem of needing to build po/POTFILES.in
> | > Allan> from a dist rather than from a CVS tree -- and this should
> | > Allan> preferably be automated or at least automatable so that
> | > Allan> Kayvan's autogenerated rpms can still be built.
> | >
> | > No, po/POTFILES.in would be in the dist (like configure is in the dist
> | > but not in cvs)
> |
> | Sure it should be in the final dist but it must only contain files found
> | in the dist. Kayvan's automation was broken by John when he left out the
> | frontends/kde dir from the dist. po/POTFILES.in was created based on the
> | files found in the cvs tree not what was actually in the dist.
> |
> | So you see we need an extra half step in the creation of a dist to ensure
> | that POTFILES.in is built in/from the dist and as a result it seems likely
> | lyx.pot and the gmo files would also need to be rebuilt _after_ this step
> | rather than as the first step in building a dist as it is now.
>
> And then you break the lyx.pot file and the po files. Not good.
So what do we do then? Make Kayvan and other dist builders do everything
manually? They then have to fix lyx.pot and po files to work with their
dist? Or do you just want to rule out any chance of ever having
port-specific dists?
How will rebuilding POTFILES.in break lyx.pot and po files?
Even if it does break them won't regenerating lyx.pot unbreak them?
They still contain all the strings from the files in the port-specific
dist at all the same line numbers. It's just some files are missing so
their entries won't be relevent. How does that break gettext?
> "forøvrig mener jeg at POTFILES.in bør genereres manuelt"
How will generating POTFILES.in manually fix anything? (Kiss goodbye to
Kayvan's automatic builds if you do)
Allan. (ARRae)
