From: Christopher Howard <christopher@librehacker.com>
To: Drew Adams <drew.adams@oracle.com>
Cc: Help Gnu Emacs Mailing List <help-gnu-emacs@gnu.org>
Subject: Re: [External] : file metadata
Date: Wed, 16 Oct 2024 07:58:17 -0800 [thread overview]
Message-ID: <87zfn459ba.fsf@librehacker.com> (raw)
In-Reply-To: Drew Adams's message of "Tue, 15 Oct 2024 21:14:32 +0000 (18 hours, 27 minutes, 26 seconds ago)"
May I ask, hopefully with sounding antagonistic, why you prefer to maintain your library on EmacsWiki rather than a git repository some where?
In the Guix distribution packaging is it is very easy to pull a library from a git repository, as well as automatically check for updates, whereas there is not tooling to scan a wiki page and try to figure what are the correct files and whether the library has changed recently. I'm sure this is why the Guix emacs-bookmark-plus package depends on the out-of-date GitHub mirror. I think the wiki itself is a git repository, but even if one wanted to download the whole wiki, the library files are not sequestered into some distinct directory where they are easy for the tooling to deal with.
You could of course say that people are free to mirror the files themselves if they want to, but that brings us back to where we are now — a mirror that has not been kept up-to-date.
--
Christopher Howard
next reply other threads:[~2024-10-16 15:58 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-10-16 15:58 Christopher Howard [this message]
2024-10-16 20:22 ` [External] : file metadata Drew Adams
-- strict thread matches above, loose matches on Subject: below --
2024-10-15 19:44 Christopher Howard
2024-10-15 21:14 ` Drew Adams
2024-10-11 22:22 Christopher Howard
2024-10-12 0:58 ` [External] : " Drew Adams
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=87zfn459ba.fsf@librehacker.com \
--to=christopher@librehacker.com \
--cc=drew.adams@oracle.com \
--cc=help-gnu-emacs@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.
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).