From: Adam Porter <adam@alphapapa.net>
To: philipk@posteo.net
Cc: emacs-devel@gnu.org, tonyzorman@mailbox.org
Subject: Re: package-vc support for :files keyword
Date: Mon, 18 Sep 2023 13:54:36 -0500 [thread overview]
Message-ID: <5f11ccd3-4f04-2f93-6f69-825e0d232944@alphapapa.net> (raw)
In-Reply-To: <871qevbhru.fsf@posteo.net>
Hi Philip, et al,
> For the record, these are all the repositories in {Non,}GNU ELPA that
> develop multiple packages in a single repository:
>
> GNU ELPA:
> http://www.dr-qubit.org/git/predictive.git
> https://github.com/oantolin/embark
> https://github.com/abo-abo/swiper
> https://github.com/abo-abo/hydra
> https://github.com/alphapapa/taxy.el.git
>
> From what I understand, there is no technical necessity for this mode of
> development? I wonder how difficult it would be to push for a
> one-package-one-repo approach.
Please note out that while `taxy' and `taxy-magit-section' are both
developed in "taxy.el.git", they are in separate branches, so there is
no need to build the two packages from a single set of files by
excluding some files and then the others.
I've chosen to keep these packages in the same repo because they are so
closely related. I'd like to be able to keep this arrangement.
Having said that, while I wouldn't personally object to dropping support
for building multiple packages from a single branch (since I don't do it
myself), I wouldn't favor doing so, because existing packages do, and it
would create more work for the authors to have to split them up.
Maybe it would be reasonable to make a new policy against building
multiple packages from a single branch, while "grandfathering" in the
existing packages that do so, if it would solve a problem for ELPA.
Thanks for your work,
Adam
next prev parent reply other threads:[~2023-09-18 18:54 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 [this message]
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
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=5f11ccd3-4f04-2f93-6f69-825e0d232944@alphapapa.net \
--to=adam@alphapapa.net \
--cc=emacs-devel@gnu.org \
--cc=philipk@posteo.net \
--cc=tonyzorman@mailbox.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/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).