From: Ruediger Meier <sweet_f_a@gmx.de>
To: Karel Zak <kzak@redhat.com>
Cc: util-linux@vger.kernel.org
Subject: Re: build-sys: minor issues
Date: Mon, 2 Jun 2014 12:33:23 +0200 [thread overview]
Message-ID: <201406021233.23463.sweet_f_a@gmx.de> (raw)
In-Reply-To: <20140602094243.GM9000@x2.net.home>
On Monday 02 June 2014, Karel Zak wrote:
> On Mon, Jun 02, 2014 at 12:56:16AM +0200, Ruediger Meier wrote:
> > 1. ./configure --enable-all-programs
> > also triggers --enable-deprecated-last. Would be nice to exclude
> > this deprecated stuff somehow.
>
> fixed, thanks for your report.
Thanks! All the recent build-sys tweaks were really helpful!
> > 2. make dist
> > changes files in source dir, which makes the git clone dirty. Would
> > be nice if we could avoid this somehow.
>
> What files? I see po/ stuff modification and it's more political
> issue than technical. The reason is that I update po/ only once
> before release (to avoid many many huge commits with irrelevant
> changes).
I have to admit that I'm not really familar with this translations.
But IMO generally it's not nice that "make dist" pollutes the git
clone.
I see 3 possibilities how to avoid this.
1. Don't track these po files in git at all. Always generate in
builddir. Put them into dist only.
2. Don't update them with "make dist". Add new target "make update-po".
3. Keep them in srcdir but update to builddir. Add a script
"commit-po-updates" to manulally move them from builddir to
srcdir from time to time.
My use case is a cronjob like this
git pull origin
./autogen.sh && ./configure && make dist
"push-tarball-to-build-host"
Because of the current git pollution I have to do always "git
reset --hard" before "autogen.sh" to not have "-dirty" suffixed version
numbers.
cu,
Rudi
next prev parent reply other threads:[~2014-06-02 10:33 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 [this message]
2014-06-03 11:27 ` Karel Zak
2014-06-03 19:46 ` Benno Schulenberg
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=201406021233.23463.sweet_f_a@gmx.de \
--to=sweet_f_a@gmx.de \
--cc=kzak@redhat.com \
--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