all messages for Guix-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Alex Kost <alezost@gmail.com>
To: Maxim Cournoyer <maxim.cournoyer@gmail.com>
Cc: guix-devel <guix-devel@gnu.org>
Subject: Re: elisp packages discovery
Date: Sat, 02 Sep 2017 23:08:28 +0300	[thread overview]
Message-ID: <873784uamb.fsf@gmail.com> (raw)
In-Reply-To: <87y3pywk27.fsf_-_@gmail.com> (Maxim Cournoyer's message of "Fri, 01 Sep 2017 10:49:20 -0400")

Maxim Cournoyer (2017-09-01 10:49 -0400) wrote:

> Hi Alex!
>
> Alex Kost <alezost@gmail.com> writes:
>
>> Maxim Cournoyer (2017-08-15 12:08 -0400) wrote:
>>
>>> On Tue, Jul 18, 2017 at 9:52 AM, Alex Kost <alezost@gmail.com> wrote:
>> [...]
>>>     A side note: this is one of the reasons why I don't like "guix.d"
>>>     sub-directory.  I think it is a useless extra level in the file
>>>     hierarchy.  If we used:
>>>
>>>       .../share/emacs/site-lisp/<package>
>>>
>>> While I agree that packaging elisp files in their own folder is
>>> cleaner, it also introduces some complexity such as the requirement
>>> to add some glue code in the Emacs site-start.el for packages
>>> discovery.
>>>
>>> This mechanism is only valid when working with a profile;
>>> at build time (say, you want to run tests which depend on other Emacs
>>> packages), another hack is required + manual fiddling.
>>>
>>> By contrast, if all of our Emacs packages were laid out flat under
>>> the usual share/emacs/site-lisp/ like it's done on other
>>> distributions,
>>
>> I wonder how many emacs packages these distributions provide and whether
>> they have any name conflicts in "site-lisp" or not.
>
> I should have researched what I said beforehand; I just looked at how
> Debian does it, and it seems they are also isolating package files in
> their own subdir under an elpa-src diretory[0], or at least going into
> that direction. Their approach is a bit different; they make use of
> package.el which ships with Emacs, so they do not need any custom code
> in site-start.

I think it would be good to reduce the size of our "site-start" code by
re-using "package.el" facilities, although removing it completely will
probably not be possible since we use non-standard directories, where
Emacs does not look for packages (I mean the user and system Guix
profiles).

> Gentoo is also using a <package> subdirectory[1]:
> /usr/share/emacs/site-lisp/package/ and rely on some custom site-start
> elisp glue for packages discovery. So, I'm not sure if there are any
> distribution actually packaging their elisp libraries directly under the
> share/emacs/site-lisp like I thought was the case. Sorry for the
> misinformation!

No problem!

> [0] https://anonscm.debian.org/cgit/pkg-emacsen/pkg/dh-elpa.git/tree/README.org
> [1] https://wiki.gentoo.org/wiki/Project:GNU_Emacs/Developer_guide

Thanks for the pointers!

-- 
Alex

      reply	other threads:[~2017-09-02 20:08 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-07-13 12:20 bug#27686: emacs-ess: Not installed in "${output}/share/emacs/site-lisp/guix.d" Adonay Felipe Nogueira
2017-07-18 13:52 ` Alex Kost
2017-07-29 20:34   ` Alex Kost
2017-08-15 14:38   ` Adonay Felipe Nogueira
2017-08-15 16:08   ` Maxim Cournoyer
2017-08-19 18:32     ` Alex Kost
2017-09-01 14:49       ` elisp packages discovery (was: bug#27686: emacs-ess: Not installed in "${output}/share/emacs/site-lisp/guix.d)" Maxim Cournoyer
2017-09-02 20:08         ` 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=873784uamb.fsf@gmail.com \
    --to=alezost@gmail.com \
    --cc=guix-devel@gnu.org \
    --cc=maxim.cournoyer@gmail.com \
    /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.