From: Chunyang Xu <xuchunyang.me@gmail.com>
To: "Clément Pit--Claudel" <clement.pit@gmail.com>
Cc: emacs-devel@gnu.org
Subject: Re: Provide rsync access to GNU ELPA for mirroring it
Date: Sun, 3 Jul 2016 15:16:58 +0800 [thread overview]
Message-ID: <CAHs_4in3V+k3M72j2d28M7J=DLkQh324qSO=Z32FZPrO+Yt0zg@mail.gmail.com> (raw)
In-Reply-To: <577813D3.6040506@gmail.com>
On Sun, Jul 3, 2016 at 3:19 AM, Clément Pit--Claudel
<clement.pit@gmail.com> wrote:
> On 2016-07-02 12:02, Chunyang Xu wrote:
>> Hello emacs-devel!
>>
>> The emacs-china user group is running an ELPA mirror [1] to provide
>> faster and more reliable connection for Chinese Emacs users.
>> Currently, it simply downloads all files through HTTP, it works well
>> for more than one month, however, mirroring through rsync is obviously
>> easier and more efficient. So please consider providing rsync access
>> to Gnu elpa.
>
> Is there a reason to not build the packets locally, instead of downloading them all from ELPA?
Good point, actually I never think about this way before, maybe this
is a good way for Gnu ELPA. git access to savannah is very slow (< 50
KiB/s) and unreliable here, I will try this way after (if) git-clone
is done. Also, I am not sure if building locally can keep old versions
of packages like GNU ELPA.
Anyway, I still think rsync is the best way to mirror.
> (Same for MELPA, btw; this is going to ruin download statistics)
MELPA itself needs 3 hours to build its 3000+ packages. Building MELPA
packages locally is not easy.
I am not very sure if we are ruining the download statistics, but the
user-agent we used is always different from Emacs/url.el/package.el
> Clément.
>
next prev parent reply other threads:[~2016-07-03 7:16 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-07-02 16:02 Provide rsync access to GNU ELPA for mirroring it Chunyang Xu
2016-07-02 19:19 ` Clément Pit--Claudel
2016-07-03 7:16 ` Chunyang Xu [this message]
2016-07-13 1:06 ` Clément Pit--Claudel
2016-07-13 2:45 ` Stefan Monnier
2016-07-13 7:14 ` Clément Pit--Claudel
2016-07-13 14:23 ` Stefan Monnier
2016-07-15 15:41 ` Stefan Monnier
2016-07-15 16:09 ` Clément Pit--Claudel
2016-07-15 16:31 ` Stefan Monnier
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='CAHs_4in3V+k3M72j2d28M7J=DLkQh324qSO=Z32FZPrO+Yt0zg@mail.gmail.com' \
--to=xuchunyang.me@gmail.com \
--cc=clement.pit@gmail.com \
--cc=emacs-devel@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).