From: Giovanni Biscuolo <g@xelera.eu>
To: "John Soo" <jsoo1@asu.edu>,
guix-devel@gnu.org, "Ludovic Courtès" <ludo@gnu.org>
Cc: GNU Guix maintainers <guix-maintainers@gnu.org>
Subject: emacs-guix (upstream) needs more love: a survey of repositories, homepage and issues
Date: Wed, 27 Apr 2022 15:16:40 +0200 [thread overview]
Message-ID: <874k2eis3r.fsf@xelera.eu> (raw)
[-- Attachment #1: Type: text/plain, Size: 5047 bytes --]
Hi all!
Executive summary: we should agree with Alex Kost to continue
development on the one and only one official package repo, web page
/and/ bug report (and dismiss the old ones, converting them read-only of
necessary, with a note on the old pages) system because we now have two
/diverging/ packages with the very same name and two (three?) different
bug reporting platforms... and that's very confusing.
AFAIU since 2021-01-11 [1] the new official home of emacs-guix is on
Savannah as a Guix sub-project [2]; Alex Kost agreed [3] and told us
that:
--8<---------------cut here---------------start------------->8---
As for me, I will continue to use my version of Emacs-Guix and to adjust
it for my needs.
--8<---------------cut here---------------end--------------->8---
and that's what he is doing (see below), so now "officially" we have
/two/ packages named emacs-guix: the official one at Savannah and the
"personal" one maintained by Alex.
The official version is hosted here:
https://git.savannah.gnu.org/cgit/guix/emacs-guix.git
but this is /not/ what is packaged in Guix now: we are packaging the
"personal" Alex version since 2021-05-01 (commit 57681f1640) since I've
done my little research (grepping for emacs-guix in commit message) and
found this changes in the URL of the origin (list in reverse timeline
order):
* 399e3ee7b7 (gnu: emacs-guix: Update to 0.5.2.5-c9aef52.) dated Thu Aug
26 21:52:49 2021 (current) contains this diff:
--8<---------------cut here---------------start------------->8---
(uri (git-reference
- ;; TODO: Use the official version when it has a new home
- (url "https://github.com/alezost/guix.el")
+ (url "https://gitlab.com/emacs-guix/emacs-guix.git")
--8<---------------cut here---------------end--------------->8---
* 57681f1640 (gnu: emacs-guix: Update to 0.5.2-4.8ce6d21.) dated Sat May
1 15:56:41 2021 contains this diff:
--8<---------------cut here---------------start------------->8---
;; TODO: Use the official version when it has a new home
- (url "https://github.com/jsoo1/guix.el")
+ (url "https://github.com/alezost/guix.el")
--8<---------------cut here---------------end--------------->8---
* f98e3adcd5 (gnu: emacs-guix: Update to 0.5.2.3-a694fdb.) dated Sat Dec
12 20:56:46 2020 contains this diff:
--8<---------------cut here---------------start------------->8---
- (url "https://gitlab.com/emacs-guix/emacs-guix")
+ ;; TODO: Use the official version when it has a new home
+ (url "https://github.com/jsoo1/guix.el")
--8<---------------cut here---------------end--------------->8---
Looking at the commit log summary on the web, the officlal and Alex
repositories have diverged meanwhile, with different commits on both;
the official one have two new commits from you Ludo' (that's why I'm
directly messaging you Ludo'... you (and others) are probably using the
official version /not/ installed from Guix upstream ;-) ).
Also, the official (personal ?) web site for emacs-guix is
https://emacs-guix.gitlab.io/website/; in the home page we read: «Source
code of Emacs-Guix: https://gitlab.com/emacs-guix/emacs-guix»
Also, the "official" (personal ?) home page references to MELPA as one
of the install method, and on MELPA we have https://melpa.org/#/guix
referencing
https://github.com/alezost/guix.el/tree/c9aef52121b458297e70bb50f49f7276b4a8d759
for the source code. Fortunately the GitLab and GitHub remotes are kept
in sync (by Alex I guess) so we non not have a third repo :-)
Also, "official" web page contains a manual
https://emacs-guix.gitlab.io/website/manual/latest/emacs-guix.html
that is /not/ obtained using the official repo (AFAIU the manual still
have the same content, anyway)
Also, the "personal" issues (/and/ merge requests) are here:
https://gitlab.com/emacs-guix/emacs-guix/-/issues /and/ here:
https://github.com/alezost/guix.el/issues and...
...they are not (obviously) in sync, so users now have to search on tho
different platforms (three considering guix-devel) for past _upstream_
bug reports; AFAIK we don't even have an official bug reporting mailing
list on gnu.org (is it supposed to be guix-bugs?)
So now we have an official emacs-guix on Savannah (lacking an official
web page and a bug-report mailing list) and the "personal" version of
emacs-guix on a different "personal" reporitory hosted on two remotes:
one on GitLab, referenced in the home page, and one on GitHub,
referenced in the MELPA project page.
IMHO we should definitely fix this situation.
Thanks! Gio'
[1] Message id:871rer5xxv.fsf@asu.edu
[2] Message id:87bldu43ta.fsf@asu.edu (same thread of the above message)
[3] Message id:87v9cum99w.fsf@gmail.com
--
Giovanni Biscuolo
Xelera IT Infrastructures
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 849 bytes --]
next reply other threads:[~2022-04-27 13:17 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-04-27 13:16 Giovanni Biscuolo [this message]
2022-04-27 14:01 ` emacs-guix (upstream) needs more love: a survey of repositories, homepage and issues John Soo
2022-04-27 15:31 ` Ryan Prior
2022-04-28 16:31 ` Giovanni Biscuolo
2022-04-28 8:08 ` Ludovic Courtès
2022-04-28 16:27 ` Giovanni Biscuolo
2022-04-29 10:12 ` zimoun
2022-05-23 14:39 ` Ludovic Courtès
2022-05-23 15:36 ` Kaelyn
2022-05-26 15:01 ` Giovanni Biscuolo
2022-05-26 23:15 ` Kaelyn
2022-05-27 6:32 ` Giovanni Biscuolo
2022-05-26 20:40 ` Théo Maxime Tyburn
2022-05-27 6:45 ` Giovanni Biscuolo
2022-05-27 9:21 ` Théo Maxime Tyburn
2022-09-02 16:13 ` Simon Streit
2022-10-06 14:00 ` Ludovic Courtès
2022-10-26 11:24 ` Théo Tyburn
2022-05-30 15:33 ` Ludovic Courtès
2022-06-03 22:04 ` Théo Maxime Tyburn
2022-06-07 17:42 ` Kaelyn
2022-06-08 11:15 ` Kaelyn
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=874k2eis3r.fsf@xelera.eu \
--to=g@xelera.eu \
--cc=guix-devel@gnu.org \
--cc=guix-maintainers@gnu.org \
--cc=jsoo1@asu.edu \
--cc=ludo@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/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.