From: Alex Kost <alezost@gmail.com>
To: Oleg Pykhalov <go.wigust@gmail.com>
Cc: guix-devel@gnu.org
Subject: Re: 29/88: gnu: Add emacs-let-alist.
Date: Mon, 07 May 2018 20:11:51 +0300 [thread overview]
Message-ID: <87muxbwfu0.fsf@gmail.com> (raw)
In-Reply-To: <87wowg3cq3.fsf@gmail.com> (Oleg Pykhalov's message of "Sun, 06 May 2018 20:39:32 +0300")
Oleg Pykhalov (2018-05-06 20:39 +0300) wrote:
> Alex Kost <alezost@gmail.com> writes:
>
> […]
>
>> I don't understand what mechanism you mean. Why it cannot simply be
>> removed?
>
> ‘guix import elpa’ should remove ‘let-alist’ or ‘guix lint’ should
> notify ‘let-alist’ is already present in current Emacs.
I don't think we should bother about it. Potentially, there always may
be some packages in ELPA that are kept there just for backward
compatibility (i.e., for the older versions of Emacs). I really think
it is unnecessary to keep track of such packages and treat them
specially on the Guix side.
>>> ‘let-alist’
>>> shouln't clutter much if it stays in Guix package collection for a time.
>>
>> But why should it stay? Since Emacs includes it, and it is not a
>> dependency for any package, I don't see a reason to keep it.
>
> Because people will not package it again until Guix ‘import’ or ‘lint’
> handle ‘let-alist’.
OK, I see your point. I have an opposite opinion: I would definitely
check if a package is a part of Emacs before trying to package it. And
I think 'let-alist' should be removed, since it is a useless package.
Anyway, if other people will not answer, I think you can do whatever
seems appropriate to you.
--
Alex
prev parent reply other threads:[~2018-05-07 17:11 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20180502172100.16240.36842@vcs0.savannah.gnu.org>
[not found] ` <20180502172109.5B497204D2@vcs0.savannah.gnu.org>
2018-05-03 19:13 ` 29/88: gnu: Add emacs-let-alist Alex Kost
2018-05-03 19:26 ` Pierre Neidhardt
2018-05-04 6:13 ` Oleg Pykhalov
2018-05-04 8:39 ` Pierre Neidhardt
2018-05-04 5:52 ` Oleg Pykhalov
2018-05-04 18:50 ` Oleg Pykhalov
2018-05-06 16:55 ` Alex Kost
2018-05-06 17:39 ` Oleg Pykhalov
2018-05-07 17:11 ` Alex Kost [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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87muxbwfu0.fsf@gmail.com \
--to=alezost@gmail.com \
--cc=go.wigust@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.