From: Andreas Enge <andreas@enge.fr>
To: "Ludovic Courtès" <ludo@gnu.org>
Cc: bug-guix@gnu.org
Subject: Re: Texlive
Date: Tue, 5 Feb 2013 18:04:13 +0100 [thread overview]
Message-ID: <201302051804.13252.andreas@enge.fr> (raw)
In-Reply-To: <87ip691c95.fsf@gnu.org>
[-- Attachment #1: Type: text/plain, Size: 2794 bytes --]
Am Sonntag, 3. Februar 2013 schrieb Ludovic Courtès:
> OK. So the catalogs are built once for all during the build, right?
Yes, over the full content of the texlive distribution.
> Perhaps “data” would be a (slightly) more descriptive name?
Okay, why not; I used "share" because normally the subdirectories end up in
"share".
> Looks like your approach works fine, but maybe we could still ask Karl
> Berry to see what he thinks?
This would be an opportunity to ask him a few questions, so why not.
> > But everything is FSF and Debian free. How about adding a license
> > "mixed" or "fsf-free"? Or do you have a good suggestion?
> Yes, or we could just export the ‘license’ constructor from (guix
> licenses). That would allow us to make a custom <license> objects when
> needed, like here.
Or we could leave it empty in some way; just call it "free"? It is clear
that we will only package free software; so a license field that can only
state "a collection of free licenses, for details, see the source" conveys
really no information at all. So I do not see what to construct here. My
suggestion:
(define fsf
(license "fsf"
"http://www.gnu.org/licenses/"
"A collection of free licenses according to the FSF, see the
source for details."))
> And the good thing is that now that you’ve done TeX Live and netpbm,
> you’ll find that Xorg is really piece of cake. :-)
After looking at it, my impression is that at least the build process
should be much easier (once the right order of installation determined).
> > (define-public texlive
> >
> > (package
> >
> > (name "texlive")
> > (version "2012")
> Should be 20120701 no?
There is one edition per year, commonly refered to as "TeX Live 20YY"; so
there is no reason to go into more datails.
> (with-directory-excursion bin
> (for-each symlink
> '("pdftex" "pdftex" "xetex" "luatex" "luatex.1")
> '("latex" "pdflatex" "xelatex" "lualatex" "lualatex.1")))
Very elegant, thanks for the suggestion! But actually, this manual symlink
phase has become superfluous by some directoty related configure flags I
just added.
> > (mkdir "texlive-extra")
> > (chdir "texlive-extra")
> > (apply unpack (list #:source texlive-extra))
> > (apply patch-source-shebangs (list #:source
> > texlive-extra)) (system* "mv" "tlpkg" share)
> > (chdir "../..")
>
> When you have paired ‘cd foo’ and ‘cd ..’, you can instead use
> ‘with-directory-excursion’, as shown above.
Okay. Here it is less useful, since "unpack" changes directories, so a
"chdir ".."" will remain in any case.
Andreas
[-- Attachment #2: Type: text/html, Size: 12681 bytes --]
next prev parent reply other threads:[~2013-02-05 17:04 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-02-03 16:56 Texlive Andreas Enge
2013-02-03 18:30 ` Texlive Ludovic Courtès
2013-02-05 17:04 ` Andreas Enge [this message]
2013-02-05 17:11 ` Texlive Andreas Enge
2013-02-05 21:03 ` Texlive Ludovic Courtès
2013-02-05 22:03 ` Texlive Andreas Enge
2013-02-05 22:51 ` Texlive Ludovic Courtès
2013-02-05 19:30 ` Texlive Andreas Enge
2013-02-05 21:11 ` Texlive Ludovic Courtès
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
List information: https://guix.gnu.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=201302051804.13252.andreas@enge.fr \
--to=andreas@enge.fr \
--cc=bug-guix@gnu.org \
--cc=ludo@gnu.org \
/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 public inbox
https://git.savannah.gnu.org/cgit/guix.git
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).