public inbox for util-linux@vger.kernel.org
 help / color / mirror / Atom feed
From: Benno Schulenberg <bensberg@justemail.net>
To: Karel Zak <kzak@redhat.com>
Cc: Ruediger Meier <sweet_f_a@gmx.de>,
	"Util-Linux" <util-linux@vger.kernel.org>
Subject: Re: build-sys: minor issues
Date: Tue, 03 Jun 2014 21:46:14 +0200	[thread overview]
Message-ID: <1401824774.18762.124788753.6397C030@webmail.messagingengine.com> (raw)
In-Reply-To: <20140603112732.GR9000@x2.net.home>


On Tue, Jun 3, 2014, at 13:27, Karel Zak wrote:
> On Mon, Jun 02, 2014 at 12:33:23PM +0200, Ruediger Meier wrote:
> > 1. Don't track these po files in git at all. Always generate in
> >    builddir. Put them into dist only.
> 
>  No, I'm sure we want to have .po files in the git, it's part of the package.

Well, I think it's nice to have copies of those files in many repos around the
globe, but it's not really needed.  And thus several GNU packages (coreutils,
grep, tar) have chosen to drop the PO files from their version control.  The
files get fetched from the TP at release time.

> > 2. Don't update them with "make dist". Add new target "make update-po".
> 
>  Well, I use "make distcheck" to generate the final release tarballs
>  and it would be nice to keep it usable :-)

Easy: add another target, "make release", that does an update-po and
then distcheck.  :)

Benno

-- 
http://www.fastmail.fm - Send your email first class


  reply	other threads:[~2014-06-03 19:46 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-06-01 22:56 build-sys: minor issues Ruediger Meier
2014-06-02  0:33 ` Ruediger Meier
2014-06-02  9:48   ` Karel Zak
2014-06-02 11:05     ` Ruediger Meier
2014-06-03 10:42   ` Karel Zak
2014-06-04  9:33     ` Ruediger Meier
2014-06-02  9:42 ` Karel Zak
2014-06-02 10:33   ` Ruediger Meier
2014-06-03 11:27     ` Karel Zak
2014-06-03 19:46       ` Benno Schulenberg [this message]
2014-06-04  8:38         ` Karel Zak
2014-06-03 13:09 ` Ruediger Meier
2014-06-04  9:26   ` Karel Zak
2014-06-04  9:48     ` Ruediger Meier

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=1401824774.18762.124788753.6397C030@webmail.messagingengine.com \
    --to=bensberg@justemail.net \
    --cc=kzak@redhat.com \
    --cc=sweet_f_a@gmx.de \
    --cc=util-linux@vger.kernel.org \
    /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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox