From: Jules Tamagnan <jtamagnan@gmail.com>
To: 71924@debbugs.gnu.org
Subject: bug#71924: 31.0.50; elpa.gnu.org has misleading link to bbdb source code
Date: Wed, 03 Jul 2024 11:06:47 -0700 [thread overview]
Message-ID: <87sewqmjt4.fsf@gmail.com> (raw)
---
* Background
This might be expected but I found it a bit confusing so figured I would
open a bug report in case it is not expected.
The high level issue is that it seems like the elpa website is pointing
to the wrong version of the bbdb source code.
* Problem
The `bbdb` package is defined in elpa as pulling from nongnu elpa. This
can be seen here -
https://git.savannah.gnu.org/cgit/emacs/elpa.git/tree/elpa-packages?h=main#n89
However the link to `bbdb`'s source code from the elpa website
(http://elpa.gnu.org/packages/bbdb.html) points to the gnu elpa version
of the source code:
https://git.savannah.gnu.org/cgit/emacs/elpa.git/?h=externals/bbdb.
This causes confusion because the website does not point to the true
source code that would be installed.
This further causes confusion because both versions of `bbdb` are
extremely different notably the elpa version of bbdb contains a
`bbdb-site.el` file
(https://git.savannah.gnu.org/cgit/emacs/elpa.git/tree/lisp/bbdb-site.el?h=externals/bbdb)
whereas the non-gnu elpa version contains a `bbdb-site.el.in` file
(https://git.savannah.nongnu.org/cgit/bbdb.git/tree/lisp/bbdb-site.el.in)
* Desired solutions
1. The elpa website should link to the bbdb source code that is defined
in elpa-packages.
2. Both versions of the elpa source code:
https://git.savannah.gnu.org/cgit/emacs/elpa.git/tree/?h=externals/bbdb, and
https://git.savannah.nongnu.org/cgit/bbdb.git/tree/, should be reconciled.
I'd be willing to tackle solution 1 and possibly solution 2 but it isn't
clear to me where the source code for the elpa website is such that it
can be modified to point to the expected URL. It also isn't clear to me
if we should be keeping both versions of the source code or consolidate
since it seems like the version on gnu.org is no longer in use.
Best,
Jules
---
In GNU Emacs 31.0.50 (build 1, x86_64-pc-linux-gnu, GTK+ Version
3.24.42, cairo version 1.18.0)
Repository revision: 9cb2a2040888c28587bed2b0902d9da90720f9a0
Repository branch: master
Windowing system distributor 'The X.Org Foundation', version 11.0.12101013
System Description: NixOS 24.11 (Vicuna)
next reply other threads:[~2024-07-03 18:06 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-07-03 18:06 Jules Tamagnan [this message]
2024-07-13 21:46 ` bug#71924: 31.0.50; elpa.gnu.org has misleading link to bbdb source code Jeremy Bryant via Bug reports for GNU Emacs, the Swiss army knife of text editors
2024-07-24 20:31 ` Jules Tamagnan
2024-07-28 11:59 ` Philip Kaludercic
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=87sewqmjt4.fsf@gmail.com \
--to=jtamagnan@gmail.com \
--cc=71924@debbugs.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 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).