From: Rob Browning <rlb@defaultvalue.org>
To: Glenn Morris <rgm@gnu.org>, Paul Eggert <eggert@cs.ucla.edu>
Cc: emacs-devel@gnu.org
Subject: Re: Possibility of a ${srcdir}/info/dir target race?
Date: Thu, 23 Oct 2014 10:20:24 -0500 [thread overview]
Message-ID: <87oat2izif.fsf@trouble.defaultvalue.org> (raw)
In-Reply-To: <l1d29je3np.fsf@fencepost.gnu.org>
Glenn Morris <rgm@gnu.org> writes:
> (Does the Debian build process really need to diverge from the normal
> tarfile build process so much?)
It's quite likely that the way I handle things can be improved, but the
current approach is due to:
- The DFSG split (unfortunately)
- History/accretion[1]
- Debian's need to keep regularly updated auto* files (architectures)
- My desire to maintain the package as branches of the upstream git
repository (via git-dpm)
[1] As an example (if I don't misremember), at least in the past the
build process might alter the shipped .elc files in the source tree,
which caused difficulties with respect to the Debian diff (also
affected by the fact that Debian patches some .el files -- though
I've been steadily reducing that).
However I eventually just switched to a brute-force approach, where
we make three entire copies of the source in
debian/build-{x,nox,lucid}, so that may not be an issue anymore.
Hope this helps
--
Rob Browning
rlb @defaultvalue.org and @debian.org
GPG as of 2011-07-10 E6A9 DA3C C9FD 1FF8 C676 D2C4 C0F0 39E9 ED1B 597A
GPG as of 2002-11-03 14DD 432F AE39 534D B592 F9A0 25C8 D377 8C7E 73A4
next prev parent reply other threads:[~2014-10-23 15:20 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-10-22 19:13 Possibility of a ${srcdir}/info/dir target race? Rob Browning
2014-10-22 20:11 ` Stefan Monnier
2014-10-22 21:22 ` Glenn Morris
2014-10-22 23:18 ` Rob Browning
2014-10-22 23:55 ` Rob Browning
2014-10-23 3:41 ` Paul Eggert
2014-10-23 5:32 ` Glenn Morris
2014-10-23 5:49 ` Glenn Morris
2014-10-23 15:20 ` Rob Browning [this message]
2014-10-23 5:38 ` Glenn Morris
2014-10-23 6:36 ` Paul Eggert
2014-10-23 15:22 ` Rob Browning
2014-10-23 15:43 ` Rob Browning
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=87oat2izif.fsf@trouble.defaultvalue.org \
--to=rlb@defaultvalue.org \
--cc=eggert@cs.ucla.edu \
--cc=emacs-devel@gnu.org \
--cc=rgm@gnu.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.
Code repositories for project(s) associated with this external index
https://git.savannah.gnu.org/cgit/emacs.git
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
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.