Development discussion of WireGuard
 help / color / mirror / Atom feed
From: "Jason A. Donenfeld" <Jason@zx2c4.com>
To: Daniel Kahn Gillmor <dkg@fifthhorseman.net>
Cc: Christian Hesse <mail@eworm.de>,
	WireGuard mailing list <wireguard@lists.zx2c4.com>
Subject: Re: [PATCH 1/1] tools: remove DESTDIR for autodetection
Date: Wed, 4 Jan 2017 22:06:10 +0100	[thread overview]
Message-ID: <CAHmME9p5E57NiVtdYDacViuDJhtFOuG5pWq1hhHJQbd5aTT0LA@mail.gmail.com> (raw)
In-Reply-To: <87a8b6k07f.fsf@alice.fifthhorseman.net>

On Wed, Jan 4, 2017 at 10:02 PM, Daniel Kahn Gillmor
<dkg@fifthhorseman.net> wrote:
> why are we checking either place?  It's entirely possible that my
> dedicated build farm doesn't have any bash completion mechanisms
> installed, even if my development system does.

Yes, the concept of auto-detection is "broken". But it's useful as a
default, for people doing `make && make install` on their dev
machines. Packagers should always set these types of flags explicitly,
as with autotools.

  reply	other threads:[~2017-01-04 20:57 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-01-04 18:50 distro packaging, makefiles, deps, systemd, new tools Jason A. Donenfeld
2017-01-04 20:14 ` [PATCH 1/1] tools: remove DESTDIR for autodetection Christian Hesse
2017-01-04 20:26   ` Jason A. Donenfeld
2017-01-04 21:02   ` Daniel Kahn Gillmor
2017-01-04 21:06     ` Jason A. Donenfeld [this message]
2017-01-04 21:18       ` Jason A. Donenfeld
2017-01-04 21:16 ` distro packaging, makefiles, deps, systemd, new tools Daniel Kahn Gillmor
2017-01-05 14:02 ` Dan Lüdtke
2017-01-06 23:01   ` Jason A. Donenfeld
2017-01-11 16:46     ` Dan Lüdtke

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=CAHmME9p5E57NiVtdYDacViuDJhtFOuG5pWq1hhHJQbd5aTT0LA@mail.gmail.com \
    --to=jason@zx2c4.com \
    --cc=dkg@fifthhorseman.net \
    --cc=mail@eworm.de \
    --cc=wireguard@lists.zx2c4.com \
    /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;
as well as URLs for NNTP newsgroup(s).