From mboxrd@z Thu Jan 1 00:00:00 1970 From: Federico Beffa Subject: Texlive Date: Sun, 15 Mar 2015 10:50:05 +0100 Message-ID: Mime-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Return-path: Received: from eggs.gnu.org ([2001:4830:134:3::10]:37137) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1YX5BP-0006lj-8D for guix-devel@gnu.org; Sun, 15 Mar 2015 05:50:08 -0400 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1YX5BO-00084E-8R for guix-devel@gnu.org; Sun, 15 Mar 2015 05:50:07 -0400 Received: from mail-lb0-x22b.google.com ([2a00:1450:4010:c04::22b]:35592) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1YX5BO-000821-1D for guix-devel@gnu.org; Sun, 15 Mar 2015 05:50:06 -0400 Received: by lbcgn8 with SMTP id gn8so3463412lbc.2 for ; Sun, 15 Mar 2015 02:50:05 -0700 (PDT) List-Id: "Development of GNU Guix and the GNU System distribution." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: guix-devel-bounces+gcggd-guix-devel=m.gmane.org@gnu.org Sender: guix-devel-bounces+gcggd-guix-devel=m.gmane.org@gnu.org To: andreas@enge.fr Cc: Guix-devel Andreas Enge writes: > Hello, > > the attached patch does what its commit message says. It is the fruit of many > trials and discussions with Ludovic. The tricky thing was to link to the > kpsewhich binary in texlive-bin, but to make it take its configuration file > texmf.cnf from texlive-data. I ended up wrapping all binaries and providing > them with the suitable value of TEXMFCNF. > > The real goal of the patch is to make it easy to create a second package > texlive-small in a second step. This package shall inherit from texlive, > but have as input texlive-texmf-small, which is created as texlive-texmf, > but after deleting a big chunk of data; I would say, all the documentation > and most of the fonts. Such a smaller package could be a native input for > packages creating their documentation from a latex source, for instance. If I understand correctly then the two packages, texlive and texlive-small, will essentially be independent. It would be nice to have an incremental strategy with a hierarchy, say texlive-base, texlive-common, texlive-extra, texlive-all, where each package is non-overlapping with other ones. Then a new functionality to aggregate packages into a new package where you specify which packages to include. Something like guix package --aggregate texlive --with texlive-base texlive-common ... This would be useful for packages with plug-ins, to bundle compilers with a selection of libraries, ... Regards, Fede