Pierre Neidhardt <m...@ambrevar.xyz> writes:
> Robert Vollmert <r...@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
