From: Tony Zorman <tonyzorman@mailbox.org>
To: Philip Kaludercic <philipk@posteo.net>
Cc: emacs-devel@gnu.org
Subject: Re: package-vc support for :files keyword
Date: Tue, 19 Sep 2023 16:17:41 +0200 [thread overview]
Message-ID: <87o7hyl01m.fsf@hyperspace> (raw)
In-Reply-To: <87pm2ebldd.fsf@posteo.net>
On Tue, Sep 19 2023 08:47, Philip Kaludercic wrote:
> Tony Zorman <tonyzorman@mailbox.org> writes:
>
> [… 42 lines elided …]
>
>> This is not just for multiple packages in a single repository—at least
>> one has to somewhat broaden what "multiple packages" means. Some
>> packages include small shims for bigger projects, and inadvertently
>> require them as dependencies. The original issue[1] on the
>> vc-use-package repo mentions org-ql[2], more specifically its helm
>> integration in the form of helm-org-ql.el. Some people might not want to
>> pull down helm as a dependency just for one file that they are not going
>> to use anyways.
>>
>> I'm not sure how common of a situation this actually is, but at least
>> for the big completion frameworks—helm and ivy—it's not totally unheard
>> of.
>
> Hmm, this is interesting example that I was not familiar with. As an
> alternative idea, do you think that using `:ignored-files' like
> elpa-admin.el could be useful? You could exclude all the files with
> "soft-dependencies", that wouldn't be scraped in `package-vc--unpack-1'
> when looking for dependency files.
Overall, I think this would be the better (even best) approach, yes.
(I also consider executing external shell commands during build-time an
anti pattern, I just got the feeling that making package-vc support
`:ignored-files' wasn't on the table—glad to realise that I was wrong!)
--
Tony Zorman | https://tony-zorman.com/
next prev parent reply other threads:[~2023-09-19 14:17 UTC|newest]
Thread overview: 30+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-06-10 10:53 package-vc support for :files keyword Daniel Fleischer
2023-06-10 13:23 ` Philip Kaludercic
2023-06-10 14:20 ` Daniel Fleischer
2023-06-11 8:55 ` Philip Kaludercic
2023-06-11 9:30 ` Daniel Fleischer
2023-06-11 10:24 ` Philip Kaludercic
2023-09-18 7:25 ` Tony Zorman
2023-09-18 9:10 ` Philip Kaludercic
2023-09-18 14:43 ` Tony Zorman
2023-09-18 15:52 ` Philip Kaludercic
2023-09-18 18:54 ` Adam Porter
2023-09-19 8:37 ` Philip Kaludercic
2023-09-19 12:23 ` Adam Porter
2023-09-19 13:56 ` Philip Kaludercic
2023-09-19 14:14 ` Adam Porter
2023-09-18 19:40 ` Tony Zorman
2023-09-19 8:47 ` Philip Kaludercic
2023-09-19 13:48 ` Adam Porter
2023-09-19 14:00 ` Philip Kaludercic
2023-09-19 14:17 ` Tony Zorman [this message]
2023-09-20 7:32 ` Philip Kaludercic
2023-09-21 13:28 ` Tony Zorman
2023-09-21 16:32 ` Philip Kaludercic
[not found] ` <87jzsgm82h.fsf@hyperspace>
2023-09-24 14:31 ` Philip Kaludercic
2023-09-25 13:32 ` Tony Zorman
2023-09-27 14:03 ` Philip Kaludercic
2023-10-04 6:44 ` Tony Zorman
2023-09-19 22:51 ` Jonas Bernoulli
2023-09-22 12:38 ` Stefan Kangas
2023-09-22 13:26 ` Philip Kaludercic
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://www.gnu.org/software/emacs/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87o7hyl01m.fsf@hyperspace \
--to=tonyzorman@mailbox.org \
--cc=emacs-devel@gnu.org \
--cc=philipk@posteo.net \
/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/emacs.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).