From mboxrd@z Thu Jan 1 00:00:00 1970 From: Andreas Enge Subject: Re: Texlive Date: Mon, 16 Mar 2015 19:54:41 +0100 Message-ID: <20150316185441.GE17577@debian> References: <20150315104707.GA8872@debian> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Return-path: Received: from eggs.gnu.org ([2001:4830:134:3::10]:56960) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1YXaA6-0000NH-MX for guix-devel@gnu.org; Mon, 16 Mar 2015 14:54:55 -0400 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1YXaA2-0002fH-70 for guix-devel@gnu.org; Mon, 16 Mar 2015 14:54:50 -0400 Received: from mout.kundenserver.de ([212.227.17.10]:50484) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1YXaA1-0002eB-Tt for guix-devel@gnu.org; Mon, 16 Mar 2015 14:54:46 -0400 Content-Disposition: inline In-Reply-To: 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: Federico Beffa Cc: Guix-devel On Sun, Mar 15, 2015 at 12:16:58PM +0100, Federico Beffa wrote: > Just to clarify: the idea would be that the "--aggregate" command > would produce a new package in the store. The new in store package > would inherit the content of the "--with" packages, but with the > possibility to replace some parts (e.g. ls-R, ...) with the help of > some phase. The new parts would only be residing in the new aggregate > and the user would install the new aggregate instead of the other > individual parts. I see. As mentioned by Ludovic, this seems like a big hammer to solve a smallish problem. Something easier could be done in the texlive module already. I considered something along the following lines: - Write a procedure that takes a (possibly empty) list of subdirectories to delete from texlive-texmf, and that returns the corresponding package. For the current texlive-texmf, one would pass an empty list, for texlive-texmf-small, it could be a list containing "doc", for instance. - Write a procedure that takes a texlive-texmf type input and creates a corresponding texlive package, and use it for texlive and texlive-small. This would be theoretically very flexible, but I think we want to limit the number of texlive packages exposed to the public; personally, I would say to two... Andreas