From: kkebreau@posteo.net
To: Leo Famulari <leo@famulari.name>
Cc: 46107-done@debbugs.gnu.org
Subject: [bug#46107] [PATCH 6/6] gnu: Add avogadro2.
Date: Fri, 29 Jan 2021 11:28:08 -0500 [thread overview]
Message-ID: <5d4c2474cdc539f2792e70b0dbcf7fc4@posteo.net> (raw)
In-Reply-To: <YBNfWJOg1qda1OsH@jasmine.lan>
On 2021-01-28 20:05, Leo Famulari wrote:
> On Mon, Jan 25, 2021 at 10:24:28PM -0500, Kei wrote:
>> Done and done! Thanks for reviewing and commenting. Avogadro is
>> clear for
>> removal, especially since it doesn't seem to build anymore.
>
> Do you know if avogradro2 is suitable as a "drop-in" replacement for
> avogadro? If so, we could mark it as superseded by avogadro2, and then
> it would be automatically updated in users' profiles when they do `guix
> pull && guix upgrade`.
I think so. Development efforts seem to have been focused on Avogadro 2
for
several years now, with little or no maintenance of the original
Avogadro. This
2018 community survey [0] indicates the developers' full commitment to
Avogadro 2, so marking it as superseding avogadro is recommended.
[0]: https://avogadro.cc/news/community-survey-results/
next prev parent reply other threads:[~2021-01-29 16:29 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-01-25 21:20 [bug#46107] [PATCH 1/6] gnu: Add spglib Kei Kebreau
2021-01-25 21:22 ` [bug#46107] [PATCH 2/6] gnu: Add mmtf-cpp Kei Kebreau
2021-01-25 21:22 ` [bug#46107] [PATCH 3/6] gnu: Add molequeue Kei Kebreau
2021-01-25 22:18 ` Leo Famulari
2021-01-26 3:21 ` Kei
2021-01-25 21:22 ` [bug#46107] [PATCH 4/6] gnu: Add libmsym Kei Kebreau
2021-01-25 21:22 ` [bug#46107] [PATCH 5/6] gnu: Add avogadrolibs Kei Kebreau
2021-01-25 21:22 ` [bug#46107] [PATCH 6/6] gnu: Add avogadro2 Kei Kebreau
2021-01-25 22:19 ` Leo Famulari
2021-01-26 3:24 ` bug#46107: " Kei
2021-01-29 1:05 ` [bug#46107] " Leo Famulari
2021-01-29 16:28 ` kkebreau [this message]
2021-01-29 20:20 ` Leo Famulari
2021-01-25 22:17 ` [bug#46107] [PATCH 1/6] gnu: Add spglib Leo Famulari
2021-01-26 3:20 ` Kei
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=5d4c2474cdc539f2792e70b0dbcf7fc4@posteo.net \
--to=kkebreau@posteo.net \
--cc=46107-done@debbugs.gnu.org \
--cc=leo@famulari.name \
/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.