From: Philip Kaludercic <philipk@posteo.net>
To: Daniel Fleischer <danflscr@gmail.com>
Cc: emacs-devel@gnu.org
Subject: Re: package-vc support for :files keyword
Date: Sat, 10 Jun 2023 13:23:28 +0000 [thread overview]
Message-ID: <87sfaz1men.fsf@posteo.net> (raw)
In-Reply-To: <m2fs6z7fm8.fsf@gmail.com> (Daniel Fleischer's message of "Sat, 10 Jun 2023 13:53:35 +0300")
Daniel Fleischer <danflscr@gmail.com> writes:
> Hi, I've been testing package-vc support in Emacs 29. It's clear that
> this feature is inspired by 3rd party packages that help users install
> packages from external forges.
I have never used any of the other packages managers, primarily because
they seem to peruse different goals. The primary motivation for
package-vc is to make it easy to hack on packages that are already
available on an ELPA and contribute these changes upstream via commands
like `package-vc-prepare-patch'. The fact that it can be used as the
primary method for package.el to fetch sources is an "unintended"
consequence.
> Also, it makes sense that the Melpa
> recipe specification compatibility is not a goal.
Right, as the primary technical inspiration for package-vc has been
elpa-admin, and therefore we (re-)use GNU ELPA-style package
specifications.
> However, I do think
> the `:files' keyword is very useful to have, and was wondering whether
> it's planned, maybe in master?
No, just like `:ignored-files' I do not see a sensible way to implement
it without compromising on the primary goal mentioned above. Generally
speaking, this is a style of package development that {GNU,NonGNU} ELPA
would like to advise against perusing, in favour of a
one-repo-per-package approach. Do you have a specific reason why you
think that something like `:{ignored-,}files' are useful in general
(i.e. not just because of the contingent fact that MELPA has popularised
this form of development).
But just like :make and :shell-command, or use-package support was not
intended in the beginning, I don't insist on anything as long as a
good compromise can be found. I just have my doubts, since supporting
this would probably run against a number of basic assumptions that
package-vc was written around.
> Thanks,
next prev parent reply other threads:[~2023-06-10 13:23 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 [this message]
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
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87sfaz1men.fsf@posteo.net \
--to=philipk@posteo.net \
--cc=danflscr@gmail.com \
--cc=emacs-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/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.