all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Xiyue Deng <manphiz@gmail.com>
To: Michael Heerdegen <michael_heerdegen@web.de>
Cc: Michael Heerdegen via "Emacs development discussions."
	<emacs-devel@gnu.org>
Subject: Re: Question regarding load-path handling for ELPA packages
Date: Sun, 26 May 2024 22:30:37 -0700	[thread overview]
Message-ID: <87jzjfhldu.fsf@debian-hx90.lan> (raw)
In-Reply-To: <87a5kcwudl.fsf@web.de> (Michael Heerdegen's message of "Sun, 26 May 2024 15:55:02 +0200")

Hi Michael,

Michael Heerdegen <michael_heerdegen@web.de> writes:

> Xiyue Deng <manphiz@gmail.com> writes:
>
>> > [...] doesn't add subdirectories recursively.  Or does it?
>> This is the content of subdirs.el:
>>
>> ,----
>> | (if (fboundp 'normal-top-level-add-subdirs-to-load-path)
>> |     (normal-top-level-add-subdirs-to-load-path))
>> `----
>
> Ok indeed - `normal-top-level-add-to-load-path'
> vs. `normal-top-level-add-subdirs-to-load-path', I see.
>
>
>> [...] With this support dh-elpa can keep the same directory layout as
>> ELPA for package with source files in nested directories as well.
>
> I see.  Then I think the more you mimic (or call) what package.el does
> the saver you are.
>
>> > Any package still can add subdirectories explicitly.  In sum I see
>> > more disadvantages.
>>
>> I agree with you arguments here.  My initial thoughts for adding
>> subdirectories are mainly to give developer some flexibilities to
>> organize the source code, but if subdirectories can be added explicitly
>> then it's fine.  Do you know where how that's done is documented for
>> ELPA?
>
> Sorry, no, and I didn't find anything.  Could be that it's undocumented.
> At least I did not find an explicit description of how subdirectories of
> the content directory are handled.

Thanks for help checking!  It's not urgent as we don't have an actual
use case yet.  Will revisit should the need comes up.

>
>
> Michael.

-- 
Xiyue Deng



  reply	other threads:[~2024-05-27  5:30 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-05-10  3:09 Question regarding load-path handling for ELPA packages Xiyue Deng
2024-05-17 16:30 ` Xiyue Deng
2024-05-17 17:33   ` Michael Heerdegen via Emacs development discussions.
2024-05-17 21:32     ` Xiyue Deng
2024-05-18 15:18       ` Michael Heerdegen via Emacs development discussions.
2024-05-18 21:04         ` Michael Heerdegen via Emacs development discussions.
2024-05-19  7:29         ` Xiyue Deng
2024-05-19 20:11           ` Michael Heerdegen via Emacs development discussions.
2024-05-20  6:06             ` Xiyue Deng
2024-05-22 15:53               ` Michael Heerdegen
2024-05-23  1:42                 ` Xiyue Deng
2024-05-26 13:55                   ` Michael Heerdegen
2024-05-27  5:30                     ` Xiyue Deng [this message]
2024-05-17 21:33   ` Michael Heerdegen via Emacs development discussions.

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=87jzjfhldu.fsf@debian-hx90.lan \
    --to=manphiz@gmail.com \
    --cc=emacs-devel@gnu.org \
    --cc=michael_heerdegen@web.de \
    /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/emacs.git
	https://git.savannah.gnu.org/cgit/emacs/org-mode.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.