From: Hartmut Goebel <h.goebel@crazy-compilers.com>
To: Hilton Chain <hako@ultrarare.space>, Wojtek Kosior <koszko@koszko.org>
Cc: Andreas Enge <andreas@enge.fr>, Andy Tai <atai@atai.org>,
guix-devel@gnu.org
Subject: Re: poetry: python-poetry?
Date: Sat, 5 Aug 2023 10:39:49 +0200 [thread overview]
Message-ID: <307014c7-04aa-3b0f-3f07-363bb3e77c16@crazy-compilers.com> (raw)
In-Reply-To: <87leew25tp.wl-hako@ultrarare.space>
Am 31.07.23 um 04:05 schrieb Hilton Chain:
> I think we can define library and CLI program separately, since Python
> libraries usually need to propagate some inputs, while CLI programs in
> /bin and /sbin do not, as they are wrapped by the build system.
I like the idea of "hiding" dependencies behind the script and not have
them pollute the library path. And indeed I just thought about something
like this when packaging vagrant (which is a rube-program).
If we implement such a thing, IMHO it should become a wrapper function,
doing all the magic, so the program would defined as simple as
(define-public xxx
(python-scripts-from-package
python-xxx
"xxx" "xxx3" "xxx-admin")) ; selecting scripts might be
useful/necessary
And of course we should start providing such a thing for other
languages, too.
--
Regards
Hartmut Goebel
| Hartmut Goebel | h.goebel@crazy-compilers.com |
| www.crazy-compilers.com | compilers which you thought are impossible |
next prev parent reply other threads:[~2023-08-05 8:40 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-07-27 4:25 poetry: python-poetry? Andy Tai
2023-07-27 6:56 ` Andreas Enge
2023-07-27 18:10 ` Wojtek Kosior via Development of GNU Guix and the GNU System distribution.
2023-07-31 2:05 ` Hilton Chain
2023-07-31 2:05 ` Hilton Chain
2023-08-05 8:39 ` Hartmut Goebel [this message]
2023-07-27 7:03 ` Lars-Dominik Braun
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=307014c7-04aa-3b0f-3f07-363bb3e77c16@crazy-compilers.com \
--to=h.goebel@crazy-compilers.com \
--cc=andreas@enge.fr \
--cc=atai@atai.org \
--cc=guix-devel@gnu.org \
--cc=hako@ultrarare.space \
--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.
Code repositories for project(s) associated with this public inbox
https://git.savannah.gnu.org/cgit/guix.git
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).