From: "Stephen J. Turnbull" <stephen@xemacs.org>
To: Lennart Borgman <lennart.borgman@gmail.com>
Cc: Eli Zaretskii <eliz@gnu.org>,
Angelo Graziosi <angelo.graziosi@alice.it>,
"Richard M. Stallman" <rms@gnu.org>,
emacs-devel@gnu.org
Subject: Re: Emacs 23.4 Updated Windows Binaries published
Date: Tue, 07 Feb 2012 02:01:41 +0900 [thread overview]
Message-ID: <8739anzyiy.fsf@uwakimon.sk.tsukuba.ac.jp> (raw)
In-Reply-To: <CANbX365845TtQKA-LvdFX-T_fzK4_A+GNfE_3ggxYnpoOMnEXQ@mail.gmail.com>
Lennart Borgman writes:
> It says "through the same place", not "at the same place". And it also
> tells what to do if the source is not on the same server as the object
> code.
>
> I really do not understand. I would be glad if you explained
> further.
You may be right. At least, by "same place" I mean "via relative
URI", and I've always read 6(d) that way, but that's clearly my
mistake since it does refer to textual instructions.
The question about a third party's sources, though, I think there's
some ambiguity there. "You" are required to provide and ensure
availability of the sources; I've always interpreted that as meaning
you need to have access to the server where the archive is hosted, and
the phrase about "operated by a third party" is intended to avoid the
excessive burden (for most folks) of maintaining a host. Rather, you
can use Savannah or SourceForge, as long as you do the work of
maintaining the copy.
If the intent is in fact to allow a third party's copy to be used, ok,
you're technically right. But I would consider the necessary legal
arrangements to be prohibitively expensive, compared to a rental
server or a project on Savannah or SourceForge.
> Updating the DOI-like URI would indeed be problematic since it could
> still be used for old distributed object. I guess you have to create
> new numbers for every ojbect distribution.
Yes. But this isn't that hard; you would use some kind of universal
ID, like the bzr revid (not revno).
> Ok, I never understood it that way, but you may be right. However even
> Launchpad seems to get an easy way to download a zip file instead of
> using Bazaar soon.
Sure, that would certainly satisfy the "equivalent copying" requirement.
next prev parent reply other threads:[~2012-02-06 17:01 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-02-05 16:34 Emacs 23.4 Updated Windows Binaries published Angelo Graziosi
2012-02-05 16:52 ` Eli Zaretskii
2012-02-05 17:12 ` Angelo Graziosi
2012-02-05 17:23 ` Juanma Barranquero
2012-02-06 5:09 ` Christoph Scholtes
2012-02-05 19:10 ` Lennart Borgman
2012-02-05 20:48 ` Eli Zaretskii
2012-02-05 21:24 ` Lennart Borgman
2012-02-06 4:01 ` Eli Zaretskii
2012-02-06 3:46 ` Stephen J. Turnbull
2012-02-06 4:15 ` Lennart Borgman
2012-02-06 5:22 ` Stephen J. Turnbull
2012-02-06 5:42 ` Lennart Borgman
2012-02-06 6:26 ` Paul Eggert
2012-02-06 7:12 ` Stephen J. Turnbull
2012-02-06 7:46 ` Stephen J. Turnbull
2012-02-06 13:49 ` Lennart Borgman
2012-02-06 15:46 ` Stephen J. Turnbull
2012-02-06 13:47 ` Lennart Borgman
2012-02-06 15:33 ` Stephen J. Turnbull
2012-02-06 15:53 ` Lennart Borgman
2012-02-06 17:01 ` Stephen J. Turnbull [this message]
2012-02-06 21:40 ` Lennart Borgman
2012-02-07 9:53 ` Richard Stallman
2012-02-07 13:31 ` Lennart Borgman
2012-02-07 15:57 ` Paul Eggert
-- strict thread matches above, loose matches on Subject: below --
2012-02-05 1:04 Christoph Scholtes
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=8739anzyiy.fsf@uwakimon.sk.tsukuba.ac.jp \
--to=stephen@xemacs.org \
--cc=angelo.graziosi@alice.it \
--cc=eliz@gnu.org \
--cc=emacs-devel@gnu.org \
--cc=lennart.borgman@gmail.com \
--cc=rms@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).