all messages for Guix-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Catonano <catonano@gmail.com>
To: Alex Kost <alezost@gmail.com>
Cc: guix-devel@gnu.org
Subject: Re: [PATCH] Emacs Smartparens
Date: Wed, 18 May 2016 11:24:19 +0200	[thread overview]
Message-ID: <CAJ98PDxiUg3qh3y1=Q7TsrOMTMY981fQqAAmn5bVnuX5y6BS+w@mail.gmail.com> (raw)
In-Reply-To: <87futfn304.fsf@gmail.com>

[-- Attachment #1: Type: text/plain, Size: 1028 bytes --]

2016-05-18 11:12 GMT+02:00 Alex Kost <alezost@gmail.com>:

> Catonano (2016-05-18 01:44 +0300) wrote:
>
> 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.
>

I think I saw a file requiring the ruby mode.


> >>
> > > 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.
>
>
That's what I thought too and the patch attached to the previous message
does exactly this.

It uses the emacs build system without caring for Cask, Travis or anything

The dash library is in the propagated inputs

[-- Attachment #2: Type: text/html, Size: 1669 bytes --]

  reply	other threads:[~2016-05-18  9:24 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-05-16 13:32 [PATCH] Emacs Smartparens Catonano
2016-05-16 13:58 ` Catonano
2016-05-16 14:35 ` Alex Kost
2016-05-17 22:44   ` Catonano
2016-05-18  9:12     ` Alex Kost
2016-05-18  9:24       ` Catonano [this message]
2016-05-19  8:54         ` Alex Kost

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

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to='CAJ98PDxiUg3qh3y1=Q7TsrOMTMY981fQqAAmn5bVnuX5y6BS+w@mail.gmail.com' \
    --to=catonano@gmail.com \
    --cc=alezost@gmail.com \
    --cc=guix-devel@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 external index

	https://git.savannah.gnu.org/cgit/guix.git

This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.