unofficial mirror of help-guix@gnu.org 
 help / color / mirror / Atom feed
From: Moritz Tacke <moritz.tacke@gmail.com>
To: Wojtek Kosior <koszko@koszko.org>
Cc: help-guix@gnu.org
Subject: Re: Python packages
Date: Tue, 03 Jan 2023 18:03:28 +0100	[thread overview]
Message-ID: <87fscr35zq.fsf@duckling> (raw)
In-Reply-To: <20230103172047.38eec02e.koszko@koszko.org>

You did, thank you very much!


Wojtek Kosior <koszko@koszko.org> writes:

> [[PGP Signed Part:Undecided]]
> Thanks for the details, Moritz. I'll try to clarify everything for you.
> Although you sent your response just to me, I'm adding the help-guix
> mailing list back into the CC field of the email (so that others can
> see and perhaps add some useful advice at some point).
>
> So, Guix uses its own repository for packages. Although it is a special
> kind of package manager (a transactional one), in this specific regard
> it is just as every conventional distro's package manager (e.g. APT,
> RPM) — it needs given program to be packaged by someone and added to
> its repository for it to be directly available to users. Apparently,
> nobody has packaged WFDB yet, hence `guix search` gives you nothing.
>
> `guix import`, on the other hand, is a tool meant for people who want
> to package stuff by themselves. Its target audience is both packagers
> and advanced users who are able and willing to package the missing
> software by themselves. In fact, those 2 roles can (and should) overlap
> :)
>
> So, `guix import` is a tool that just aids in making a Guix package. It
> tries to guess some things and it cannot guarantee it will guess
> correctly (since sources like PyPI often lack all the information
> required to automatically make a working package). The generated .scm
> files are therefore meant to be reviewed and edited by the user.
>
> Once you get everything to work, you can (and are encouraged to) help
> others by submitting the new package definition for inclusion in Guix.
> This, of course, requires a bit more effort (cloning the Guix' git repo,
> placing your package definition in the proper file under
> `gnu/packages/`, etc. More information here[1]. Once you get through
> this, others will be able to `guix search` the package :)
>
> Don't be surprised if many useful pieces of software are not yet in
> Guix. You can look up the number of packages in Guix, Debian and NixOS.
> Guix is a younger distro and therefore has way fewer packages ¯\_(ツ)_/¯
>
> I hope I helped
>
> Wojtek
>
> [1] https://guix.gnu.org/manual/en/html_node/Contributing.html
>
> -- (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!           #42: blessed Rafał Chyliński
> Poznaj świętych krakowskich!  #42: błogosławiony Rafał Chyliński
> https://pl.wikipedia.org/wiki/Rafał_Chyliński
> -- (sig_end)
>
>
> On Tue, 3 Jan 2023 11:33:24 +0100
> Moritz Tacke <moritz.tacke@gmail.com> wrote:
>
>> Sure!
>> I'm currently trying to install the WFDB python library. It is hosted on
>> PyPI (pypi.org/project/wfdb/), but I can't find it using "guix search".
>> What I did then was to use "guix import", which created a .scm-file. This
>> file was not yet sufficient to use it directly for installation, therefore
>> I had to modify the file (import some other files, change a problem in the
>> license statement). This lead to a .scm-file I could use to install the
>> module from the PyPi repository. Somehof I had the impression that I was
>> not using the tools in the right way, e.g. why "guix import" returned a
>> file that was not complete (but, instead, needed some quite mechanical
>> modifications from my side). I was hoping that, somehow, there would be a
>> way where I can packages from PyPi directly, with one single guix command.
>> 
>> On Mon, Jan 2, 2023 at 10:50 PM Wojtek Kosior <koszko@koszko.org> wrote:
>> 
>> > > 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)
>> >  
>
>
> [[End of PGP Signed Part]]



      reply	other threads:[~2023-01-03 17:04 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
     [not found]   ` <CANZtOB0X7D6TxfjuZrg+LomHEF8zCAhGV-hT0o6nL+COQdz4Bg@mail.gmail.com>
2023-01-03 16:20     ` Wojtek Kosior via
2023-01-03 17:03       ` Moritz Tacke [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=87fscr35zq.fsf@duckling \
    --to=moritz.tacke@gmail.com \
    --cc=help-guix@gnu.org \
    --cc=koszko@koszko.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).