unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Philip Kaludercic <philipk@posteo.net>
To: Jonas Bernoulli <jonas@bernoul.li>
Cc: emacs-devel@gnu.org
Subject: Re: Adding package-vc to ELPA
Date: Mon, 17 Apr 2023 16:24:42 +0000	[thread overview]
Message-ID: <87fs8yh3xx.fsf_-_@posteo.net> (raw)
In-Reply-To: <87sfde7lh4.fsf@posteo.net> (Philip Kaludercic's message of "Wed,  05 Apr 2023 10:59:51 +0200")

Philip Kaludercic <philipk@posteo.net> writes:

> Jonas Bernoulli <jonas@bernoul.li> writes:
>
>> Philip Kaludercic <philipk@posteo.net> writes:
>>
>>> Jonas Bernoulli <jonas@bernoul.li> writes:
>>>
>>>> Hello,
>>>
>>> Hi, hope I can add a few useful comments here.
>>>
>>>> I would like to request that "package.el" be added to GNU Elpa as a
>>>> "core" package.  This would make new features available to users who are
>>>> stuck on older Emacs releases and it would even bring us one step closer
>>>> to being able to make backward incompatible changes in the future.
>>>>
>>>> Some examples for why that would be desirable:
>>>>
>>>> - A recent addition that could be useful is the new "package-vc.el"
>>>>   (which I think should be distributed as part of the `package' package,
>>>>   but it could also be distributed as a separate core package).
>>>
>>> This will be difficult, since package-vc depends on the new "vc-clone"
>>> function, which would also have to be provided on ELPA to work.
>>
>> The simplest way to deal with that, while still making the latest
>> Package available to users of older Emacs releases, would be to *not*
>> include package-vc.el in the Package package.
>>
>> Going one step further we could make package-vc available as a separate
>> package.  That would not be of much use *now*, but future improvements
>> would then be available to users of Emacs 29.
>
> I would in principle be interested in supporting this.
>
>> I had a look at vc-clone and a few vc-*-clone.  They seem trivial
>> enough to backport, either as part of Compat or in package-vc.el.

I have put some more though into this, and I don't think adding the new
VC functionality to Compat or package-vc.el would be a good idea.
Beside vc-clone we would also need `vc-prepare-patch' and the
"last-change" method.  What would be imaginable would be to add the
package to ELPA and make it depend on Emacs 29?  Would that sound
useful?



  parent reply	other threads:[~2023-04-17 16:24 UTC|newest]

Thread overview: 23+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-03-30 13:42 Request to add Package to GNU ELPA Jonas Bernoulli
2023-03-30 16:40 ` Felician Nemeth
2023-03-30 17:37   ` Philip Kaludercic
2023-03-30 17:32 ` Philip Kaludercic
2023-03-31 17:15   ` Jonas Bernoulli
2023-04-05  8:59     ` Philip Kaludercic
2023-04-05 14:13       ` Jonas Bernoulli
2023-04-05 18:07         ` Philip Kaludercic
2023-04-05 18:26         ` Philip Kaludercic
2023-04-05 21:08           ` Philip Kaludercic
2023-04-06 15:46             ` Philip Kaludercic
2023-04-06 21:36               ` Stefan Monnier
2023-04-07  7:23                 ` Philip Kaludercic
2023-04-07 15:39                   ` Stefan Monnier
2023-04-08  8:24                     ` Philip Kaludercic
2023-04-09 15:29                       ` Stefan Monnier
2023-04-09 17:27                         ` Philip Kaludercic
2023-04-07 10:07                 ` Philip Kaludercic
2023-04-06 11:41           ` Jonas Bernoulli
2023-04-17 16:24       ` Philip Kaludercic [this message]
2023-09-16 17:20         ` Adding package-vc to ELPA Stefan Kangas
2023-09-17  8:02           ` Philip Kaludercic
2023-03-30 19:10 ` Request to add Package to GNU ELPA chad

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=87fs8yh3xx.fsf_-_@posteo.net \
    --to=philipk@posteo.net \
    --cc=emacs-devel@gnu.org \
    --cc=jonas@bernoul.li \
    /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).