all messages for Guix-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Leo Famulari <leo@famulari.name>
To: Stephen Scheck <singularsyntax@gmail.com>
Cc: help-guix <help-guix@gnu.org>
Subject: Re: Package workspace relocation
Date: Mon, 16 Nov 2020 15:56:47 -0500	[thread overview]
Message-ID: <20201116205647.GA24897@jasmine.lan> (raw)
In-Reply-To: <CAKjnHz1stHdbhehmOOVtyB75BB5_xDLd-uFaGWsPsRMH9SbjmQ@mail.gmail.com>

On Mon, Nov 16, 2020 at 03:15:46PM -0500, Stephen Scheck wrote:
> Is there a way to relocate the package build workspace for a Git clone
> source, e.g.:
> 
>     (package
>       (name "my-package")
>       (version "0.0.1")
>       (source (origin
>                       (method git-fetch)
>                       (uri (git-reference
>                          (url "https://github.com/my-package")))
>                          (file-name (git-file-name name version))
> 
> This results in a path like `<guix-build-temp>/my-package-0.0.1` but
> because of idiosyncrasies in the project's build system, I need for it to
> be relocated to something like `<guix-build-temp>/foo/bar/my-package-0.0.1`.
> 
> How can I do this?

I'm not sure that I fully understand what you are asking.

However, the location of the build directory is controlled by the TMPDIR
variable, which is set in the environment of the guix-daemon. You can
set it to any location that you want.

An alternative per-package approach is to add a build phase before the
'unpack' phase and do something like `mkdir -p foo/bar && chdir
foo/bar`.


  reply	other threads:[~2020-11-16 20:57 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-11-16 20:15 Package workspace relocation Stephen Scheck
2020-11-16 20:56 ` Leo Famulari [this message]
2020-11-16 21:56   ` Stephen Scheck
2020-11-16 23:09     ` zimoun
2020-11-17  7:23       ` Efraim Flashner
2020-11-17 13:07         ` zimoun

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=20201116205647.GA24897@jasmine.lan \
    --to=leo@famulari.name \
    --cc=help-guix@gnu.org \
    --cc=singularsyntax@gmail.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.
Code repositories for project(s) associated with this external index

	https://git.savannah.gnu.org/cgit/guix.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.