Re: GHC packages' inputs leak in guix shell

2023-08-28 Thread Saku Laesvuori
On Mon, Aug 28, 2023 at 01:40:14PM +0200, Simon Tournier wrote: > Hi, > > On Thu, 24 Aug 2023 at 19:16, Saku Laesvuori wrote: > >> > Running `guix shell --pure ghc-esqueleto -D ghc-bytestring-builder` > >> > results in an environment that has the base64-bytestring package (from > >> >

Re: documentation in TeX Live collections

2023-08-28 Thread Andreas Enge
Hello, Am Mon, Aug 28, 2023 at 06:54:35PM +0200 schrieb Nicolas Goaziou: > Emmanuel Beffara writes: > > I don't understand how "out" and "doc" are different in this respect. The > > "out" output of a collection meta-package has no content of its own and it > > only serves to gather the "out"

Re: documentation in TeX Live collections

2023-08-28 Thread Nicolas Goaziou
Nicolas Goaziou writes: > Emmanuel Beffara writes: >>> In any case, I suggest to write a proper bug report for this. Hopefully, >>> someone with better understanding about the implications of GUIX_TEXMF >>> will be able to solve this. >> >> I can do that for the texdoc behaviour. By the way,

Re: GHC packages' inputs leak in guix shell

2023-08-28 Thread Simon Tournier
Hi, On Thu, 24 Aug 2023 at 19:16, Saku Laesvuori wrote: >> > Running `guix shell --pure ghc-esqueleto -D ghc-bytestring-builder` >> > results in an environment that has the base64-bytestring package (from >> > ghc-base64-bytestring) visible, even though it is not listed on listed >> > the

Re: documentation in TeX Live collections

2023-08-28 Thread Nicolas Goaziou
Emmanuel Beffara writes: > I don't understand how "out" and "doc" are different in this respect. The > "out" output of a collection meta-package has no content of its own and it > only serves to gather the "out" outputs of its inputs. Similarly, the "doc" > output would have no content of its

Re: documentation in TeX Live collections

2023-08-28 Thread Emmanuel Beffara
Hello, Thanks for the instructive feedback! De Nicolas Goaziou le 28/08/2023 à 13:01: > Every texlive-* package comes with its documentation, in a separate > output. "doc" output are not uncommon at all in Guix. Therefore, > I disagree with the inconsistency you're talking about. Ok, I admit I

Re: documentation in TeX Live collections

2023-08-28 Thread Nicolas Goaziou
Hello, Emmanuel Beffara writes: > Yet, as far as I know, most packages in Guix (apart from texlive-* ones) come > with their documentation, so it feels somewhat inconsistent. Every texlive-* package comes with its documentation, in a separate output. "doc" output are not uncommon at all in

Re: documentation in TeX Live collections

2023-08-28 Thread Emmanuel Beffara
Hello, De Nicolas Goaziou le 27/08/2023 à 12:13: > > Apparently, all individual packages have a specific "doc" output but > > collections and schemes do not and they don't have them as inputs either. So > > we end up with an installation with no documentation > > It sounds like a good default to

Re: Problem with Shepherd after `guix home reconfigure`

2023-08-28 Thread Tanguy LE CARROUR
Hi Hilton, Quoting Hilton Chain (2023-08-25 09:34:09) > On Fri, 25 Aug 2023 14:59:03 +0800, > Tanguy LE CARROUR wrote: > > I have no XDG "log" variable, but the `shepherd.log` in > > `~/.local/state/log/` > > contains today's log, so… I guess it can write to the log folder. > > The strange