From: Alex Kost <alezost@gmail.com>
To: Federico Beffa <beffa@ieee.org>
Cc: Guix-devel <guix-devel@gnu.org>
Subject: Re: Why do we use ".../share/emacs/site-lisp/guix.d/"?
Date: Sun, 08 May 2016 22:51:10 +0300 [thread overview]
Message-ID: <871t5cwcpd.fsf@gmail.com> (raw)
In-Reply-To: <CAKrPhPPgg0xnwBLrm+2DSOhoirJjPYCjTQ0L6ZoLy6vbpFf4WQ@mail.gmail.com> (Federico Beffa's message of "Sun, 8 May 2016 18:23:19 +0200")
Federico Beffa (2016-05-08 19:23 +0300) wrote:
> On Sun, May 8, 2016 at 12:33 PM, Alex Kost <alezost@gmail.com> wrote:
>> I should have asked this when emacs-build-system was introduced. Why
>> does it put emacs packages in sub-directories of
>> "/share/emacs/site-lisp/guix.d"? It looks more natural to me just to
>> use "/share/emacs/site-lisp".
>>
>> I don't see any potential conflicts here: some packages will put their
>> elisp files right in the site-lisp dir (gnu-build-system does it by
>> default), and emacs-build-system can just use
>> "/share/emacs/site-lisp/<package>" sub-directories.
>>
>> "guix.d" seems redundant to me. What do people think?
>
> Answer here:
>
> https://lists.gnu.org/archive/html/guix-devel/2015-06/msg00398.html
No it is not :-) I think you miss-understood my point.
You said that we should put emacs packages into subdirectories, and I
agree with this, but instead of the current:
".../site-lisp/guix.d/PACKAGE-NAME-VERSION/"
I suggest to use:
".../site-lisp/PACKAGE-NAME-VERSION/"
i.e., to remove "guix.d".
--
Alex
next prev parent reply other threads:[~2016-05-08 19:51 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-05-08 10:33 Why do we use ".../share/emacs/site-lisp/guix.d/"? Alex Kost
2016-05-08 16:23 ` Federico Beffa
2016-05-08 19:51 ` Alex Kost [this message]
2016-05-08 20:06 ` Federico Beffa
2016-05-09 6:42 ` Federico Beffa
2016-05-09 9:13 ` Alex Kost
2016-05-16 21:15 ` Ludovic Courtès
2016-05-17 18:14 ` Alex Kost
2016-05-19 12:02 ` Ludovic Courtès
2016-05-20 6:53 ` Federico Beffa
2016-05-20 21:00 ` Alex Kost
2016-05-21 10:47 ` Federico Beffa
2016-05-21 21:39 ` Alex Kost
2016-05-22 20:28 ` Ludovic Courtès
2016-05-08 16:51 ` Ludovic Courtès
2016-05-08 19:58 ` 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
List information: https://guix.gnu.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=871t5cwcpd.fsf@gmail.com \
--to=alezost@gmail.com \
--cc=beffa@ieee.org \
--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 public inbox
https://git.savannah.gnu.org/cgit/guix.git
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).