[bug#32428] [PATCH] gnu: mit-scheme: Use minimal texlive-union.

[bug#32428] [PATCH] gnu: mit-scheme: Use minimal texlive-union.

[Pierre Neidhardt]

* gnu/packages/scheme.scm (mit-scheme)[native-inputs]: Replace texlive with texlive-union.
---
 gnu/packages/scheme.scm | 6 +++++-
 1 file changed, 5 insertions(+), 1 deletion(-)

diff --git a/gnu/packages/scheme.scm b/gnu/packages/scheme.scm
index b30245cce..ef94aedad 100644
--- a/gnu/packages/scheme.scm
+++ b/gnu/packages/scheme.scm
@@ -104,6 +104,10 @@
                                (find-files "src/compiler" "^make\\.")))
              (chdir "src")
              #t))
+         ;; FIXME: the texlive-union insists on regenerating fonts.  It stores
+         ;; them in HOME, so it needs to be writeable.
+         (add-before 'build 'set-HOME
+           (lambda _ (setenv "HOME" "/tmp") #t))
          (replace 'build
            (lambda* (#:key system outputs #:allow-other-keys)
              (let ((out (assoc-ref outputs "out")))
@@ -150,7 +154,7 @@
                (delete-file-recursively old-doc-dir)
                #t))))))
     (native-inputs
-     `(("texlive" ,texlive)
+     `(("texlive" ,(texlive-union (list texlive-tex-texinfo)))
        ("texinfo" ,texinfo)
        ("m4" ,m4)))
     (inputs
-- 
2.18.0

[bug#32428] [PATCH] gnu: mit-scheme: Use minimal texlive-union.

[Pierre Neidhardt]

[-- Attachment #1: Type: text/plain, Size: 285 bytes --]

I've re-used the same workaroud as emacs-ess for font generation.
A little dirty (but not too much?) maybe, but I think it's much better
than relying on the obese texlive package.

I'll merge if nobody finds anything wrong with it.

-- 
Pierre Neidhardt
https://ambrevar.xyz/

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 487 bytes --]

[bug#32428] [PATCH] gnu: mit-scheme: Use minimal texlive-union.

[Ludovic Courtès]

Hello Pierre!

Pierre Neidhardt <ambrevar@gmail.com> skribis:

> * gnu/packages/scheme.scm (mit-scheme)[native-inputs]: Replace texlive with texlive-union.
> ---
>  gnu/packages/scheme.scm | 6 +++++-
>  1 file changed, 5 insertions(+), 1 deletion(-)
>
> diff --git a/gnu/packages/scheme.scm b/gnu/packages/scheme.scm
> index b30245cce..ef94aedad 100644
> --- a/gnu/packages/scheme.scm
> +++ b/gnu/packages/scheme.scm
> @@ -104,6 +104,10 @@
>                                 (find-files "src/compiler" "^make\\.")))
>               (chdir "src")
>               #t))
> +         ;; FIXME: the texlive-union insists on regenerating fonts.  It stores
> +         ;; them in HOME, so it needs to be writeable.
> +         (add-before 'build 'set-HOME
> +           (lambda _ (setenv "HOME" "/tmp") #t))

Is this a bug in ‘texlive-union’?  Does it take time and space to
regenerate the fonts?

Otherwise the change LGTM, for ‘emacs-ess’ & co. as well, as long as we
don’t duplicate the $HOME trick dozens of times.

Thanks!

Ludo’.

[bug#32428] [PATCH] gnu: mit-scheme: Use minimal texlive-union.

[Pierre Neidhardt]

[-- Attachment #1: Type: text/plain, Size: 780 bytes --]

Hello Ludo!

Well, we might have to duplicate the trick a dozen of times... :(
Until we get a better understanding of what's going on.

My limited understanding of this is that some TeXlive packages don't build the
fonts they need at install time, only at runtime.  I don't quite understand why
that is.

It's not clear to me if it's possible to build these fonts in advance.

That said, in the present state it's only required to generate the documentation
when building the package.  While this escapes the build directory, I assume
this

Hopefully we will come with a clearer answer to this issue in the future.

I'll merge considering the workaround is much better than having a full texlive
as a dependency.

-- 
Pierre Neidhardt
https://ambrevar.xyz/

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 487 bytes --]

[bug#32428] [PATCH] gnu: mit-scheme: Use minimal texlive-union.

[Pierre Neidhardt]

[-- Attachment #1: Type: text/plain, Size: 403 bytes --]

For got to answer your first comment:
> Is this a bug in ‘texlive-union’?

I don't think this is related to texlive-union, but since I don't fully
understand the issue, I don't know if texlive-union could be tweaked to fix
this.

> Does it take time and space to regenerate the fonts?

Relatively little: < 5 seconds I'd say, less than 1MB.

-- 
Pierre Neidhardt
https://ambrevar.xyz/

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 487 bytes --]

[bug#32428] [PATCH] gnu: mit-scheme: Use minimal texlive-union.

[Ludovic Courtès]

Hello,

Pierre Neidhardt <ambrevar@gmail.com> skribis:

> My limited understanding of this is that some TeXlive packages don't build the
> fonts they need at install time, only at runtime.  I don't quite understand why
> that is.
>
> It's not clear to me if it's possible to build these fonts in advance.

Ricardo, do you have an idea about why ‘texlive-union’ fails to build
fonts in advance?  Did we encounter this issue before?

> That said, in the present state it's only required to generate the documentation
> when building the package.  While this escapes the build directory, I assume
> this
>
> Hopefully we will come with a clearer answer to this issue in the future.
>
> I'll merge considering the workaround is much better than having a full texlive
> as a dependency.

Definitely.

Thank you!

Ludo’.

[bug#32428] [PATCH] gnu: mit-scheme: Use minimal texlive-union.

[Pierre Neidhardt]

[-- Attachment #1: Type: text/plain, Size: 237 bytes --]


Oops!  Allow me to fix the missing end of the sentence:

> While this escapes the build directory, I assume this won't change anything
> regarding the reproducibility of the package.

-- 
Pierre Neidhardt
https://ambrevar.xyz/

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 487 bytes --]

[bug#32428] [PATCH] gnu: mit-scheme: Use minimal texlive-union.

[Ricardo Wurmus]

Hi Ludo,

> Pierre Neidhardt <ambrevar@gmail.com> skribis:
>
>> My limited understanding of this is that some TeXlive packages don't build the
>> fonts they need at install time, only at runtime.  I don't quite understand why
>> that is.
>>
>> It's not clear to me if it's possible to build these fonts in advance.
>
> Ricardo, do you have an idea about why ‘texlive-union’ fails to build
> fonts in advance?  Did we encounter this issue before?

I have an idea, but I haven’t been able to fix this.  This problem has
been around since the early days of using texlive-union.  It seems to me
that the TeX Live tools don’t know that the fonts are available.  This
is surprising because as far as I understand ’texlive-union’ sets up all
required environment variables and configuration files.

I discussed this with Andreas many months ago and thought that we had
pinned down the problem, but it turned out to be a dead end.  The idea
was to just set up more variables as the big texlive package does, but I
wasn’t able to convince the tools that they don’t need to rebuild the
fonts in HOME.

For other packages I was able to ignore this problem by setting HOME to
/tmp so that the tools can build the fonts cache as needed.

-- 
Ricardo

bug#32428: [PATCH] gnu: mit-scheme: Use minimal texlive-union.

[Pierre Neidhardt]

[-- Attachment #1: Type: text/plain, Size: 6 bytes --]

close

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 487 bytes --]