From mboxrd@z Thu Jan 1 00:00:00 1970 From: Alex Kost Subject: Re: [PATCH] Emacs Smartparens Date: Wed, 18 May 2016 12:12:43 +0300 Message-ID: <87futfn304.fsf@gmail.com> References: <8760ueqdeb.fsf@gmail.com> Mime-Version: 1.0 Content-Type: text/plain Return-path: Received: from eggs.gnu.org ([2001:4830:134:3::10]:50106) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1b2xX9-0003cK-GO for guix-devel@gnu.org; Wed, 18 May 2016 05:12:52 -0400 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1b2xX4-0003Pk-Du for guix-devel@gnu.org; Wed, 18 May 2016 05:12:50 -0400 Received: from mail-lb0-x241.google.com ([2a00:1450:4010:c04::241]:36492) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1b2xX4-0003Pe-5r for guix-devel@gnu.org; Wed, 18 May 2016 05:12:46 -0400 Received: by mail-lb0-x241.google.com with SMTP id r5so2366608lbj.3 for ; Wed, 18 May 2016 02:12:46 -0700 (PDT) In-Reply-To: (catonano@gmail.com's message of "Wed, 18 May 2016 00:44:19 +0200") 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" To: Catonano Cc: guix-devel@gnu.org Catonano (2016-05-18 01:44 +0300) wrote: [...] > Smartparens uses Cask. Cask is a language specific project management > tool. > > Exactly the kind of thing that Guix aims at (right ?) > > As far as I understand, Cask provides, among other things, some unit > tests running facility > > There's a target in a makefile piloting Cask to run the test. So I > understand. And there's a folder filled with .el files containing > tests to be run. > > So, the makefile, the Cask file, Make, Cask and the tests folder are > dependencies ONLY in development. > > So maybe there should be 2 outputs for this project, one vanilla > output and one for development. I think there is no need to do this. > It gets worse > > There's a specific set of dependencies for every Smartparens submode > (some languages have their own submode) so there should be an output > for each of those I think that a single output is absolutely OK: all these files (like "smartparens-haskell.el") are a part of the whole smartparens package; moreover there is no any "specific set of dependencies". The only dependency for smartparens is the "dash" library. > And finally there's also a .travis.yml file, an images folder with > some gif files in it, an org-mode file and some files ending with > .feature > > All this seems an excess to me. A developer will be able to set up an > environment with Make, Cask and other ad hoc dependencies and the > files will be present in the package anyway, even if not used. > > It's a few kilobytes anyway. I personally wouldn't care about cask, travis.yml and other files, and would just create a plain package using emacs-build-system. It will provide the same functioning package as the one you would install with Emacs (using "M-x list-packages"). I don't see a reason to deal with all the additional complexity you mentioned. -- Alex