unofficial mirror of guix-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: ludo@gnu.org (Ludovic Courtès)
To: "Thompson, David" <dthompson2@worcester.edu>
Cc: guix-devel <guix-devel@gnu.org>
Subject: Re: Making local development easy
Date: Tue, 21 Jun 2016 10:43:01 +0200	[thread overview]
Message-ID: <87lh1zc4q2.fsf@gnu.org> (raw)
In-Reply-To: <CAJ=RwfbSs1cSHDvwHZBSdYDimRnpbVAEW=04aSj6fpe=2oFniQ@mail.gmail.com> (David Thompson's message of "Thu, 26 May 2016 08:05:37 -0400")

"Thompson, David" <dthompson2@worcester.edu> skribis:

> On Thu, May 26, 2016 at 4:07 AM, Ludovic Courtès <ludo@gnu.org> wrote:
>
>> Even shorter:
>>
>>   (source "/some/file/out/there")
>>
>> or:
>>
>>   (source ".")
>
> I think there is a bug here because I've tried this at various points
> in time and it has never worked.  A pattern matcher somewhere fails
> because a string isn't considered an acceptable source object.

I haven’t experience this bug (and see "package-source-derivation, file"
in tests/packages.scm).  However, I’m happy to say that since commit
da675305ddf2ba574e309e515d18ae1f778297be, it is possible to use a
‘local-file’ there:

  (package
    ;; …
    (source (local-file "foo/bar" #:recursive? #t)))

See ‘current-guix’ in (gnu packages package-management) for an example.

Ludo’.

  reply	other threads:[~2016-06-21  8:43 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-05-24 18:25 Making local development easy Christopher Baines
2016-05-25  8:23 ` Alex Sassmannshausen
2016-05-25 15:48   ` Christopher Baines
2016-05-25 16:13   ` Leo Famulari
2016-05-25  9:29 ` Ricardo Wurmus
2016-05-25  9:34   ` Alex Sassmannshausen
2016-05-25 16:04   ` Christopher Baines
2016-05-25 18:33     ` Ricardo Wurmus
2016-05-26  8:07       ` Ludovic Courtès
2016-05-26 12:05         ` Thompson, David
2016-06-21  8:43           ` Ludovic Courtès [this message]
2016-05-25  9:36 ` Andy Wingo

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=87lh1zc4q2.fsf@gnu.org \
    --to=ludo@gnu.org \
    --cc=dthompson2@worcester.edu \
    --cc=guix-devel@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 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).