Re: distinguishing between applications and libraries

[Pierre Neidhardt]

Robert Vollmert <address@hidden> 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/

signature.asc
Description: PGP signature