all messages for Guix-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Ricardo Wurmus <rekado@elephly.net>
To: Pierre Neidhardt <mail@ambrevar.xyz>
Cc: guix-devel@gnu.org, Robert Vollmert <rob@vllmrt.net>
Subject: Re: distinguishing between applications and libraries
Date: Mon, 01 Jul 2019 23:46:18 +0200	[thread overview]
Message-ID: <87muhxv36d.fsf@elephly.net> (raw)
In-Reply-To: <87tvc6hisk.fsf@ambrevar.xyz>


Pierre Neidhardt <mail@ambrevar.xyz> writes:

> 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)

Nah, it’s not good to do this.  The use of @@ is an anti-pattern.

To completely hide a package from the UI use “hidden-package” or
“(properties ((hidden . #t)))”.

-- 
Ricardo

  reply	other threads:[~2019-07-01 21:46 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
2019-07-01 21:46       ` Ricardo Wurmus [this message]
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

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=87muhxv36d.fsf@elephly.net \
    --to=rekado@elephly.net \
    --cc=guix-devel@gnu.org \
    --cc=mail@ambrevar.xyz \
    --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 external index

	https://git.savannah.gnu.org/cgit/guix.git

This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.