unofficial mirror of help-guix@gnu.org 
 help / color / mirror / Atom feed
From: Phil <phil@beadling.co.uk>
To: help-guix <help-guix@gnu.org>
Subject: Re: Output all dependencies recursively for package
Date: Mon, 01 Feb 2021 19:36:55 +0000	[thread overview]
Message-ID: <85wnvreg14.fsf@beadling.co.uk> (raw)
In-Reply-To: <CAJ3okZ1jbVCdejPLPmQPXpkCSDNHCvnOBOs2fg=rD6gOsBjjqw@mail.gmail.com>

Thanks for all the responses on this.

In short - yes this does the job.  I should really write it in Guile:
guix refresh –list-transitive my-pkg | cut -d':' -f2 | tr ' ' '\n' | grep python | sort

I have a guix package that had originally been deployed with a python
requirements file to create a venv.

I was curious to see that, if I matched the versions in the requirements
file, in my guix package what the full set of dependent python packages
would be (i.e. those returned by pip freeze).

Obviously there are some mismatched because pip often only gives
requirements as a lower bound, where any given version of guix will
typically only contain a single current version of a package.

The specific weirdness I was looking at was my guix setup seemed to have
installed both tornado5 and tornado6 python packages packages - a situation that can't
happen in pip!

I was toying with writing a pkg2reqs.scm which would produce a python
requirements file from a Guix package.  I found it particularly useful to
create this manually when trying to decide if my move to Guix had issues
due to a slight version mismatch between PyPi and Guix,  or something
else.



  parent reply	other threads:[~2021-02-01 19:37 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-01-31 12:59 Output all dependencies recursively for package Phil
2021-01-31 15:03 ` Joshua Branson
2021-02-01  1:32   ` Tobias Geerinckx-Rice
2021-02-01  6:26     ` zimoun
2021-02-01 16:21       ` me--- via
2021-02-01 19:36       ` Phil [this message]
2021-01-31 15:30 ` Efraim Flashner
2021-01-31 19:09 ` 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

  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=85wnvreg14.fsf@beadling.co.uk \
    --to=phil@beadling.co.uk \
    --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).