From: Pierre Neidhardt <mail@ambrevar.xyz>
To: Robert Vollmert <rob@vllmrt.net>
Cc: guix-devel@gnu.org
Subject: Re: distinguishing between applications and libraries
Date: Sun, 30 Jun 2019 23:20:27 +0200 [thread overview]
Message-ID: <87tvc6hisk.fsf@ambrevar.xyz> (raw)
In-Reply-To: <19D3778D-BA32-41C9-81C9-60ECB4F3BF7E@vllmrt.net>
[-- Attachment #1: Type: text/plain, Size: 867 bytes --]
Robert Vollmert <rob@vllmrt.net> writes:
> Good point, but that breaks down once a library is used by a package
> outside that module. E.g. consider the various ghc-* packages. Running
> “guix search clock” returns `ghc-clock` and `ocaml-mtime`. The first
> needs to be public since it’s used elsewhere, the second is defined
> as public anyway. Should that change?
If you need to depend on a non-exported package, you can still
access it with
(@@ (gnu packages my-module) my-package)
> Well the real reason why it’s there lies in its reverse dependencies, no?
A library always does something, so this is what you need to explain in
the description. Unfortunately some authors don't always provide any
description for their work, in which case you might have to look at the
source :p
--
Pierre Neidhardt
https://ambrevar.xyz/
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 487 bytes --]
next prev parent reply other threads:[~2019-06-30 21:20 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-06-30 17:33 distinguishing between applications and libraries Robert Vollmert
2019-06-30 18:01 ` Pierre Neidhardt
2019-06-30 20:05 ` Robert Vollmert
2019-06-30 21:20 ` Pierre Neidhardt [this message]
2019-07-01 21:46 ` Ricardo Wurmus
2019-07-01 22:02 ` Pierre Neidhardt
2019-07-02 6:51 ` Ricardo Wurmus
2019-07-02 0:24 ` Jakob L. Kreuze
2019-07-02 6:55 ` Ricardo Wurmus
2019-07-02 15:24 ` Jakob L. Kreuze
2019-07-01 8:30 ` Danny Milosavljevic
2019-07-01 11:29 ` Pierre Neidhardt
2019-07-01 21:48 ` Ricardo Wurmus
2019-07-02 13:35 ` Robert Vollmert
2019-07-02 14:33 ` zimoun
2019-07-05 20:58 ` Ludovic Courtès
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=87tvc6hisk.fsf@ambrevar.xyz \
--to=mail@ambrevar.xyz \
--cc=guix-devel@gnu.org \
--cc=rob@vllmrt.net \
/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).