From: Vinicius Monego <monego@posteo.net>
To: Pierre Langlois <pierre.langlois@gmx.com>
Cc: 49668@debbugs.gnu.org
Subject: [bug#49668] [PATCH 1/2] gnu: emacs-org-roam: Update to 2.0.0.
Date: Wed, 21 Jul 2021 14:58:04 +0000 [thread overview]
Message-ID: <f4d0853c3a4de95127c33abef4d814926e1a1da2.camel@posteo.net> (raw)
In-Reply-To: <87mtqgsqxb.fsf@gmx.com>
Hi Pierre,
Em ter, 2021-07-20 às 20:53 +0100, Pierre Langlois escreveu:
> Given the v1 -> v2 migration requires a manual process, it might be a
> good idea to keep a v1 package for users that may want to stay on it
> for
> a little bit longer, what do you think? The author has kept a
> https://github.com/org-roam/org-roam-v1 repository for this effect.
The description of that repository says "No longer actively maintained.
" and the README recommends the migration. That is my main concern,
introducing a package that we know for a fact that is unmaintained and
don't have a schedule for removal. It feels more like a use case for a
custom channel.
Another option is to hold this update until 2.0.1 after v2 is more
widely used, though Guix users who wish to migrate now would have to
update manually in that case.
I will wait for more feedback on this.
Vinicius
next prev parent reply other threads:[~2021-07-21 15:00 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-07-20 19:31 [bug#49668] [PATCH 1/2] gnu: emacs-org-roam: Update to 2.0.0 Vinicius Monego
2021-07-20 19:33 ` [bug#49668] [PATCH 2/2] gnu: emacs-org-roam-bibtex: Update to 0.6.0 Vinicius Monego
2021-07-20 19:53 ` [bug#49668] [PATCH 1/2] gnu: emacs-org-roam: Update to 2.0.0 Pierre Langlois
2021-07-21 14:58 ` Vinicius Monego [this message]
2021-07-21 16:01 ` Pierre Langlois
2021-07-27 17:11 ` bug#49668: " Nicolas Goaziou
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=f4d0853c3a4de95127c33abef4d814926e1a1da2.camel@posteo.net \
--to=monego@posteo.net \
--cc=49668@debbugs.gnu.org \
--cc=pierre.langlois@gmx.com \
/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/guix.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.