unofficial mirror of help-guix@gnu.org 
 help / color / mirror / Atom feed
From: Julien Lepiller <julien@lepiller.eu>
To: help-guix@gnu.org, Andy Tai <atai@atai.org>
Subject: Re: package store directory in custom location
Date: Sun, 26 Feb 2023 09:23:55 +0100	[thread overview]
Message-ID: <6C6B009D-BD02-458E-9707-23A016943AD1@lepiller.eu> (raw)
In-Reply-To: <CAJsg1E-WNF4KcWQ0wGooZ7HrQ6Si+CVe=C54CJC07oXCEn5Wdg@mail.gmail.com>

Hi Andy,

so you could change the store location, but it would just create the same stone structure as /gnu/store elsewhere, with the same issues and no substitutes.

Instead you could try to create a relocatable pack of python, and untar it somewhere writable. There might be a small runtime penalty, but we're talking about python anyway :)

HTH!

Le 26 février 2023 02:03:01 GMT+01:00, Andy Tai <atai@atai.org> a écrit :
>Hi, is it possible to have  a /gnu/store/ directory for a package in a
>custom path?  A usage scenario is, say, to have a python interpreter,
>with its package directory that normally exists as
>/gnu/store/<something>, to be somewhere I specified, so it would be
>possible to use that python with python's package manager to install
>python modules as site packages specific to this python (as it is not
>easy to have all python modules available as packages in Guix)
>
>If this python can only run from the /gnu/store/... directory, trying
>to install site packages would normally fail (as /gnu/store/... is
>read only to non root user) and not good practice anyway (as
>/gnu/store/... is not meant to be user touched but only managed by
>Guix)
>


      reply	other threads:[~2023-02-26  8:24 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-02-26  1:03 package store directory in custom location Andy Tai
2023-02-26  8:23 ` Julien Lepiller [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=6C6B009D-BD02-458E-9707-23A016943AD1@lepiller.eu \
    --to=julien@lepiller.eu \
    --cc=atai@atai.org \
    --cc=help-guix@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. 
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).