unofficial mirror of guix-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: "Ludovic Courtès" <ludo@gnu.org>
To: Ricardo Wurmus <rekado@elephly.net>
Cc: guix-devel@gnu.org
Subject: Re: texlive-fetch instead of svn-fetch
Date: Wed, 06 Mar 2019 15:55:55 +0100	[thread overview]
Message-ID: <87sgw0gih0.fsf@gnu.org> (raw)
In-Reply-To: <87k1hiy7gu.fsf@elephly.net> (Ricardo Wurmus's message of "Fri, 01 Mar 2019 15:50:25 +0100")

Hey Ricardo!

Ricardo Wurmus <rekado@elephly.net> skribis:

> Tex Live packages often have a complicated source file layout.  They
> don’t usually come in a nice self-contained tarball.  Instead they are a
> mosaic of files that are sourced from different parts of the Tex Live
> SVN tree.  For many Tex Live packages the “source” field is
> insufficient, so we add lots of additional origins as native inputs.
> This makes for very ugly package definitions.  (See
> texlive-fonts-txfonts for an example.)
>
> What do you think about adding a new procedure that can fetch sources
> from different locations?  This might be done by extending SVN-FETCH or
> by adding a special TEXLIVE-FETCH that fetches sources from different
> directories in the source tree, returning them as *one* origin with one
> simple hash.

I don’t know much about the source file layout in TeX Live, but from
what you describe, a ‘texlive-fetch’ procedure that gathers files sounds
like the right approach.

Thanks,
Ludo’.

      parent reply	other threads:[~2019-03-06 14:56 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-03-01 14:50 texlive-fetch instead of svn-fetch Ricardo Wurmus
2019-03-01 14:58 ` Pierre Neidhardt
2019-03-01 15:27   ` Ricardo Wurmus
2019-03-01 15:32     ` Pierre Neidhardt
2019-03-06 14:55 ` Ludovic Courtès [this message]

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=87sgw0gih0.fsf@gnu.org \
    --to=ludo@gnu.org \
    --cc=guix-devel@gnu.org \
    --cc=rekado@elephly.net \
    /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).