unofficial mirror of help-guix@gnu.org 
 help / color / mirror / Atom feed
From: Wojtek Kosior via <help-guix@gnu.org>
To: Moritz Tacke <moritz.tacke@gmail.com>
Cc: help-guix@gnu.org
Subject: Re: Python packages
Date: Mon, 2 Jan 2023 22:50:43 +0100	[thread overview]
Message-ID: <20230102225043.7c4b3e83.koszko@koszko.org> (raw)
In-Reply-To: <87cz7ytksj.fsf@duckling>

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

> Hi,
> 
> I am trying to use guix to install packages that debian does not
> offer. However, in most cases (python modules) the package can't be
> installed directly using guix as the package file is missing. What is the
> correct way to proceed for e.g. a pypi module? I am currently creating a
> package file myself, but is this the way it's meant to be? Is there a
> standard place to store such custom scm files?
> Greetings!
> 
>                 Moritz

I'm not sure I fully and correctly understand the question. Can you
clarify what you mean by "package file is missing"? Where is it missing
from? How are you creating the packages yourself?

Wojtek

-- (sig_start)
website: https://koszko.org/koszko.html
PGP: https://koszko.org/key.gpg
fingerprint: E972 7060 E3C5 637C 8A4F  4B42 4BC5 221C 5A79 FD1A

Meet Kraków saints!           #10: blessed Hilary Januszewski
Poznaj świętych krakowskich!  #10: błogosławiony Hilary Januszewski
https://pl.wikipedia.org/wiki/Hilary_Januszewski
-- (sig_end)

[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 228 bytes --]

  reply	other threads:[~2023-01-02 21:51 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-01-01 14:01 Python packages Moritz Tacke
2023-01-02 21:50 ` Wojtek Kosior via [this message]
     [not found]   ` <CANZtOB0X7D6TxfjuZrg+LomHEF8zCAhGV-hT0o6nL+COQdz4Bg@mail.gmail.com>
2023-01-03 16:20     ` Wojtek Kosior via
2023-01-03 17:03       ` Moritz Tacke

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=20230102225043.7c4b3e83.koszko@koszko.org \
    --to=help-guix@gnu.org \
    --cc=koszko@koszko.org \
    --cc=moritz.tacke@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.
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).