unofficial mirror of help-guix@gnu.org 
 help / color / mirror / Atom feed
From: Tobias Geerinckx-Rice <me@tobias.gr>
To: Phil <phil@beadling.co.uk>
Cc: help-guix@gnu.org
Subject: Re: Shebang and python packages
Date: Fri, 04 Jun 2021 00:50:03 +0200	[thread overview]
Message-ID: <87pmx28sx0.fsf@nckx> (raw)
In-Reply-To: <87im2uk4vb.fsf@beadling.co.uk>

[-- Attachment #1: Type: text/plain, Size: 1344 bytes --]

Phil,

Phil 写道:
> As I understand it, as python is not propagated there is no
> guarantee that the version of python will be persisted in the 
> store for
> the lifetime of the profile containing (just) the python app?

Inputs are used when *building* things, not to manage their 
outputs (artefacts) once installed to the store.

References, not inputs, are how Guix automatically keeps track of 
which installed store items are live and which ones can be safely 
garbage-collected.

A reference just means the string "/gnu/store/…-foo" occurs 
anywhere in "/gnu/store/…-bar".  A patched shebang would be such a 
reference, so Guix knows your application uses Python because 
/gnu/store/…-yourapp-a.b.c contains references to 
/gnu/store/…-python-x.y.z.

Propagated-inputs are a hack that says as much as ‘when the user 
installs package A, pretend like they also asked to install 
package B in the same profile’.  That is *not* a good thing!  It's 
a work-around for broken packages and packages that would be far 
too much work to package in a more Guixy way.  Propagation causes 
all sorts of problems and makes profiles more fragile.  Avoid it.

> Have I misunderstood this?

I think so, or maybe I'm misunderstanding your problem.  Have you 
observed a problem?

Kind regards,

T G-R

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 247 bytes --]

  reply	other threads:[~2021-06-03 22:49 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-06-03 21:09 Shebang and python packages Phil
2021-06-03 21:24 ` Tobias Geerinckx-Rice
2021-06-03 21:36   ` Phil
2021-06-03 22:50     ` Tobias Geerinckx-Rice [this message]
2021-06-10 10:45       ` François J.
2021-06-13  9:16         ` Reza Housseini

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=87pmx28sx0.fsf@nckx \
    --to=me@tobias.gr \
    --cc=help-guix@gnu.org \
    --cc=phil@beadling.co.uk \
    /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).