unofficial mirror of help-guix@gnu.org 
 help / color / mirror / Atom feed
From: "François J." <francois-oss@avalenn.eu>
To: Tobias Geerinckx-Rice <me@tobias.gr>
Cc: help-guix@gnu.org
Subject: Re: Shebang and python packages
Date: Thu, 10 Jun 2021 12:45:19 +0200	[thread overview]
Message-ID: <20210610104519.tauqzervutn7hexy@noop.avalenn.eu> (raw)
In-Reply-To: <87pmx28sx0.fsf@nckx>

Hello,

On Fri, Jun 04, 2021 at 12:50:03AM +0200, Tobias Geerinckx-Rice wrote:
> 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.

Thank you for this explanation. I fighted a lot with the concept of
propagated inputs and this descriptions makes a lot of sense to me.

I am progressively thinking that propagated-input are used too much
in Guix packages. Python packages seem concerned a lot by this but I
have not used Guix enough to know if it is localized there or if it
is generalized. At least it is a risk I am just identifying on the
way Go packages are done (and makes me think about how we can evolve
go-build-system to avoid this).

I am not sure about what to do with that but reading this makes me feel
less alone.

François


  reply	other threads:[~2021-06-10 14:53 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
2021-06-10 10:45       ` François J. [this message]
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=20210610104519.tauqzervutn7hexy@noop.avalenn.eu \
    --to=francois-oss@avalenn.eu \
    --cc=help-guix@gnu.org \
    --cc=me@tobias.gr \
    /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).