Hi,
On Fri, 28 Jul 2023 02:10:38 +0800,
Wojtek Kosior via Development of GNU Guix and the GNU System distribution.
wrote:
>
> [1 <text/plain; UTF-8 (quoted-printable)>]
> > The idea is that "libraries" (or "modules") start with python-, while
> > "applications" do not emphasize the language they are written in. Calibre,
> > for instance, also is not called python-calibre.
>
> In this case it seems there are quite a few packages that go against
> this convention. 'python-pip', for example, is mostly used as a CLI
> *application*.
>
> This has been actually causing me confusion. At some point I was
> wondering how I should call a package I was writing and it seems I
> erroneously added "python-" taking example from other packages :/
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.
--8<---------------cut here---------------start------------->8---
(define-public python-xxx
(package
(name "python-xxx")
(propagated-inputs (list [...]))
[...]))
(define-public xxx
(package
(inherit python-xxx)
(name "xxx")
(propagated-inputs '())
(inputs (package-propagated-inputs python-xxx))
[...]))
--8<---------------cut here---------------end--------------->8---
Thanks
