From: Niklas Eklund <niklas.eklund@posteo.net>
To: Stefan Monnier <monnier@iro.umontreal.ca>
Cc: rms@gnu.org, emacs-devel@gnu.org
Subject: Re: Name dtache.el
Date: Fri, 20 May 2022 15:36:22 +0000 (UTC) [thread overview]
Message-ID: <e182d900-c42b-4e7a-a50a-a4701215a5fc@posteo.net> (raw)
In-Reply-To: <jwva6bc2pq5.fsf-monnier+emacs@gnu.org>
May 20, 2022 17:25:24 Stefan Monnier <monnier@iro.umontreal.ca>:
>> Although those relying on releases won't get that information then.
>> Maybe
>> one solution to that is that I release a new version and only update
>> the
>> recipe ones it has become available on ELPA?
>
> A partial solution is to make a release of `detached.el` and once
> that's
> done, make a release of `dtache.el` which `Package-Requires: ((detached
> "??"))`
Would I then need to have two different git repositories or how would you
go about doing that?
> It can made of a mostly empty file or a file containing just
> compatibility aliases.
So would we then keep both dtache and detached in the elpa-packages file
or how would that work?
Another option I could think about is making a release of the package at
its current path https://git.sr.ht/~niklaseklund/dtache which will be its
last dtache release. But just before the release I add a commit that
issues a warning that if you are running this release you are tracking
the wrong patch.
Then after the release, I remove that warning. Rename the https path to
detached.el and make a release with the new package name.
Then it should be fine to update elpas tracking. Because if they run on
the old release the should have the warning that they need to upgrade.
What do you think?
/Niklas
but embedding a warning when it loads that
>
> Stefan
next prev parent reply other threads:[~2022-05-20 15:36 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-04-27 16:35 Update URL to dtache.el package Niklas Eklund
2022-04-27 19:16 ` Tassilo Horn
2022-04-27 22:06 ` Stefan Monnier
2022-05-01 21:29 ` Niklas Eklund
2022-05-01 21:36 ` Niklas Eklund
2022-05-02 6:18 ` Stefan Monnier
2022-05-08 23:36 ` Name dtache.el Richard Stallman
2022-05-09 19:26 ` Niklas Eklund
2022-05-20 14:23 ` Niklas Eklund
2022-05-20 14:31 ` Stefan Monnier
2022-05-20 15:19 ` Niklas Eklund
2022-05-20 15:25 ` Stefan Monnier
2022-05-20 15:36 ` Niklas Eklund [this message]
2022-05-20 16:33 ` Niklas Eklund
2022-05-20 18:58 ` Stefan Monnier
2022-05-20 19:27 ` Niklas Eklund
2022-05-20 20:44 ` Niklas Eklund
2022-05-20 21:00 ` Stefan Monnier
2022-05-20 21:21 ` Niklas Eklund
2022-05-20 21:35 ` Stefan Monnier
2022-05-21 7:38 ` Niklas Eklund
2022-05-21 14:44 ` Stefan Monnier
2022-05-21 16:13 ` Niklas Eklund
2022-05-20 15:50 ` Eli Zaretskii
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=e182d900-c42b-4e7a-a50a-a4701215a5fc@posteo.net \
--to=niklas.eklund@posteo.net \
--cc=emacs-devel@gnu.org \
--cc=monnier@iro.umontreal.ca \
--cc=rms@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.