unofficial mirror of guix-patches@gnu.org 
 help / color / mirror / code / Atom feed
From: Tobias Geerinckx-Rice <me@tobias.gr>
To: leo@famulari.name, julien@lepiller.eu
Cc: 26718@debbugs.gnu.org
Subject: bug#26718: Update hexchat to 2.12.4
Date: Sun, 30 Apr 2017 23:11:24 +0200	[thread overview]
Message-ID: <3ceff414-da73-2415-a43f-62da6c8b3814@tobias.gr> (raw)
In-Reply-To: <20170430200534.GA27383@jasmine>


[-- Attachment #1.1: Type: text/plain, Size: 788 bytes --]

On 30/04/17 22:05, Leo Famulari wrote:
> Then there are changes we make in order to port software to Guix or make
> other relatively unimportant changes. If they can be done with a
> sed-like / regex substitution, we do them in build phases. It's helpful
> to keep them in Scheme, and we don't want to distribute them via `guix
> build --source`.

Ah, I never considered this as a Guix-related fix: shipping symlinks to
/usr might happen to work on some (?) other systems, but it's obviously
not how autotools should be used.

We should serve users with a --source tarball that is either already
bootstrapped or ready to be, not in some dead-end third state.

The correct answer in either case is, of course: ‘it's a silly detail,
Tobias’.

Kind regards,

T G-R


[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 504 bytes --]

  reply	other threads:[~2017-04-30 21:11 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-04-30 17:22 bug#26718: Update hexchat to 2.12.4 Julien Lepiller
2017-04-30 18:19 ` Tobias Geerinckx-Rice
2017-04-30 19:35   ` Julien Lepiller
2017-04-30 20:05     ` Leo Famulari
2017-04-30 21:11       ` Tobias Geerinckx-Rice [this message]
2017-05-01  7:52         ` Julien Lepiller
2017-05-05 20:21           ` Leo Famulari
2017-05-06 19:55             ` Leo Famulari
2017-05-06 21:08               ` Julien Lepiller
2017-05-06 22:02                 ` Tobias Geerinckx-Rice
2017-05-06  8:22 ` bug#26718: (no subject) Julien Lepiller
2017-05-06 13:48   ` Ludovic Courtès

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

  List information: https://guix.gnu.org/

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=3ceff414-da73-2415-a43f-62da6c8b3814@tobias.gr \
    --to=me@tobias.gr \
    --cc=26718@debbugs.gnu.org \
    --cc=julien@lepiller.eu \
    --cc=leo@famulari.name \
    /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 public inbox

	https://git.savannah.gnu.org/cgit/guix.git

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 read-only IMAP folder(s) and NNTP newsgroup(s).