From: Ricardo Wurmus <rekado@elephly.net>
To: Pierre Neidhardt <mail@ambrevar.xyz>
Cc: 27217@debbugs.gnu.org
Subject: bug#27217: texlive is too big
Date: Thu, 10 Jan 2019 17:11:52 +0100 [thread overview]
Message-ID: <87k1jc4hmf.fsf@elephly.net> (raw)
In-Reply-To: <87ftu04i37.fsf@ambrevar.xyz>
Pierre Neidhardt <mail@ambrevar.xyz> writes:
> TeXlive packages are provided "ready to use", they are not meant to be built.
> The .ins/.dtx are only here for potential package contributors or as a source of
> documentation, but when it comes to TeXlive, they are not used to build the
> resulting package. The .sty is (I think) always parachuted into the SVN
> repository as well.
I don’t think that’s correct. The .ins/.dtx files contain instructions
for generating files, including the .sty files, which are extracted from
the .dtx files.
> (Actually, sometimes there is no .ins/.dtx, just a .sty.)
Correct. For some “packages” there’s really just a .sty source file.
But often enough .sty files are generated.
We have both kinds of packages in tex.scm. Some where the .sty or .tex source
files are copied to the target location and some where the .sty or .tex files
are generated from the .ins/.dtx sources.
Whether a .sty or .tex file is a source file isn’t always obvious, but
sometimes they mention that they are generated from other files.
> More worrisome: some fonts don't provide their source.
For some fonts the provided format *is* the source.
> In fact, some of them
> have confusing licenses, and since the source is missing, I wouldn't call that
> "free software". But TeXlive is. That's not very consistent and a lot of FOSS
> TeXlive packages effectively depend on closed-source fonts.
I haven’t found any such cases yet. Could you show us cases where the
font license makes the font non-free?
>> I don’t see this file in the texlive SVN repository. Where is it
>> hosted?
>
> It's in Master/tlpkg/texlive.tlpdb.
> Or from CTAN:
> http://mirror.ctan.org/tex-archive/systems/texlive/tlnet/tlpkg/texlive.tlpdb.xz.
Ah, thanks.
--
Ricardo
next prev parent reply other threads:[~2019-01-10 16:13 UTC|newest]
Thread overview: 37+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-06-03 19:03 bug#27217: texlive is too big Ricardo Wurmus
2017-11-23 20:51 ` bug#27217: break up TeXlive for guix Matt Wette
2018-01-23 13:20 ` bug#27217: texlive is too big Mathieu Lirzin
2018-05-28 12:02 ` Ricardo Wurmus
2018-05-28 11:07 ` Peter Neidhardt
2018-05-28 11:58 ` Ricardo Wurmus
2018-05-28 12:53 ` Peter Neidhardt
2018-12-15 14:11 ` Pierre Neidhardt
2019-01-10 9:27 ` Ludovic Courtès
2019-01-10 9:49 ` Pierre Neidhardt
2019-01-10 12:30 ` Ricardo Wurmus
2019-01-10 12:51 ` Pierre Neidhardt
2019-01-10 15:34 ` Ricardo Wurmus
2019-01-10 16:01 ` Pierre Neidhardt
2019-01-10 16:11 ` Ricardo Wurmus [this message]
2019-01-10 17:47 ` Pierre Neidhardt
2019-01-10 18:50 ` Ricardo Wurmus
2019-01-10 18:56 ` Pierre Neidhardt
2019-01-10 19:01 ` Ricardo Wurmus
2019-01-10 11:27 ` Ricardo Wurmus
2019-01-10 12:15 ` Ludovic Courtès
2019-01-13 12:21 ` Ricardo Wurmus
2019-01-17 9:36 ` Ludovic Courtès
2019-01-17 9:41 ` Pierre Neidhardt
2019-01-17 10:39 ` Ricardo Wurmus
2019-01-17 10:43 ` Pierre Neidhardt
2019-01-17 11:01 ` Ricardo Wurmus
2019-03-02 14:13 ` Pierre Neidhardt
2019-03-03 14:32 ` Jelle Licht
2019-03-05 8:39 ` Pierre Neidhardt
2019-03-16 12:59 ` Pierre Neidhardt
2019-03-18 8:47 ` Ludovic Courtès
2019-03-19 21:36 ` Ricardo Wurmus
2019-03-20 7:47 ` Pierre Neidhardt
2019-03-22 21:01 ` Ludovic Courtès
2019-01-17 10:36 ` Ricardo Wurmus
2019-01-15 15:34 ` Ricardo Wurmus
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=87k1jc4hmf.fsf@elephly.net \
--to=rekado@elephly.net \
--cc=27217@debbugs.gnu.org \
--cc=mail@ambrevar.xyz \
/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.