I come back on this bug report because it appears that you were the only maintainer disagreeing with the proposed solution to this issue.
Your concern and explanation about the purpose of the clean target is for sure a real concern and I understand it. And, this means that if the PO(T) files are modified after a build, then you will have to recommit to your RCS so that it reflects what's in your source package. On the other hand, if you do not do so and, for instance, use "debconf-updatepo" in the build target(s), the PO files you have in your RCS are outdated. This is not good either. So, this is why I think that among both solutions, I would prefer choosing the less worse....aka the one suggested by Thomas. It seems to me that there's a grey area here with no perfect solution...unless something really completely new pops up. Of course, nothing critical here, and there are probably tons of other things that deserve more attention but, well, as translators we really don't like discovering that our work is actually unusable....because outdated. -- -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
