From: Eric Sandeen <sandeen@redhat.com>
To: Thierry Vignaud <tvignaud@mandriva.com>
Cc: Theodore Tso <tytso@mit.edu>,
ext4 development <linux-ext4@vger.kernel.org>
Subject: Re: [PATCH e2fsprogs] - remove timestamps from .po files
Date: Tue, 06 Nov 2007 08:33:33 -0600 [thread overview]
Message-ID: <47307B3D.2010708@redhat.com> (raw)
In-Reply-To: <m2sl3j1xkq.fsf@vador.mandriva.com>
Thierry Vignaud wrote:
> Eric Sandeen <sandeen@redhat.com> writes:
>
>> Another one that's been in RH/Fedora specfiles a while.
>> Remove timestamps from .po files to avoid multilib conflicts.
>> It ain't pretty but it works.
>
> Sorry but that's insane.
>
> Pos should not be updated on build. They should only be updated by
> upstream developers instead. This enable translators to catch up and
> prevent such hackery
Hrm, good point.
> Your spec file should not contain "make -C po update-po" in the first
> place.
> This is a fedora bug, not an e2fsprogs one IMHO.
>
> You introduced your own multi-lib in the first place...
Apparently there was some issue with this, once upon a time, which
resulted in our rpms needing to update the po files... I guess I need to
do a bit more code archeology / research. It looks like sct added this
when the pkg updated to 1.36, though there is no comment about why.
I inherited lots of history when I got e2fsprogs, so please forgive me
as I work through it. :)
One question though, then - what is the existing timestamp removal
mechanism for, then?
-Eric
next prev parent reply other threads:[~2007-11-06 14:33 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-11-05 21:13 [PATCH e2fsprogs] - remove timestamps from .po files Eric Sandeen
2007-11-05 22:06 ` Theodore Tso
2007-11-05 22:12 ` Eric Sandeen
2007-11-06 10:24 ` Thierry Vignaud
2007-11-06 14:33 ` Eric Sandeen [this message]
2007-11-06 14:55 ` Theodore Tso
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=47307B3D.2010708@redhat.com \
--to=sandeen@redhat.com \
--cc=linux-ext4@vger.kernel.org \
--cc=tvignaud@mandriva.com \
--cc=tytso@mit.edu \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.