unofficial mirror of guix-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: ludo@gnu.org (Ludovic Courtès)
To: Konrad Hinsen <konrad.hinsen@fastmail.net>
Cc: guix-devel@gnu.org
Subject: Re: Building from a local source code checkout
Date: Sat, 23 Dec 2017 00:07:25 +0100	[thread overview]
Message-ID: <87tvwi5ple.fsf@gnu.org> (raw)
In-Reply-To: <m1d138t3oa.fsf@fastmail.net> (Konrad Hinsen's message of "Thu, 21 Dec 2017 18:02:29 +0100")

Konrad Hinsen <konrad.hinsen@fastmail.net> skribis:

> ludo@gnu.org (Ludovic Courtès) writes:
>
>> I agree the matching-name constraint can be annoying.  The alternative
>> would be allow the user to (optionally?) specify the name of the package
>> whose source is being changed, as in:
>>
>>   guix build python-activepapers \
>>     --with-source=python-activepapers=$HOME/Dev/AP
>>
>> WDYT?
>
> Looks much clearer to me. But, as you say, this could well be optional
> if we can live with an ambiguity in the rare case of filenames containg
> an equal sign.

I’ve implemented it here:

  https://git.savannah.gnu.org/cgit/guix.git/commit/?id=3e30cdf1c35ebeb52630ec19b3b43b9e6d5ffb81

You no longer need to rename your source directory.  :-)

Ludo’.

      reply	other threads:[~2017-12-22 23:07 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-12-19 11:34 Building from a local source code checkout Konrad Hinsen
2017-12-19 17:15 ` Ludovic Courtès
2017-12-20  8:52   ` Konrad Hinsen
2017-12-20 10:19     ` Konrad Hinsen
2017-12-20 12:41       ` Carlo Zancanaro
2017-12-21  6:38         ` Konrad Hinsen
2017-12-21 10:38           ` Pjotr Prins
2017-12-21 11:20           ` Martin Castillo
2017-12-21 14:38             ` Ludovic Courtès
2017-12-21 16:53               ` Martin Castillo
2017-12-22  9:29                 ` Ludovic Courtès
2017-12-21 17:02               ` Konrad Hinsen
2017-12-22 23:07                 ` Ludovic Courtès [this message]

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=87tvwi5ple.fsf@gnu.org \
    --to=ludo@gnu.org \
    --cc=guix-devel@gnu.org \
    --cc=konrad.hinsen@fastmail.net \
    /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).