From: Jason Molenda <jason-swarelist@molenda.com>
To: Andrew Cagney <ac131313@cygnus.com>
Cc: overseers <overseers@sourceware.cygnus.com>
Subject: Re: ~ftp/private/...
Date: Sat, 30 Dec 2000 06:08:00 -0000 [thread overview]
Message-ID: <20000426013124.A4866@shell17.ba.best.com> (raw)
In-Reply-To: <3906A5F0.8535485F@cygnus.com>
On Wed, Apr 26, 2000 at 06:16:48PM +1000, Andrew Cagney wrote:
> Anyone object to me creating a ~ftp/private (/gdb) directory?
Oh oh, Mr. Carter! Me, me!
I set up sourceware without a ~ftp/private on purpose. It is easy
for maintainers or core developers to put things in private
directories needlessly, to cut themselves off from potential
contributors and muckers-at-large (who knows what those random net
people might do!) The lack of a ~ftp/private dir is not an oversight.
It's the approach we took at Cygnus for a long time[1]. It is the
wrong approach. So I didn't create a ~ftp/private dir on sourceware
to help break people of these habits.
[1] To be fair, everyone did it this way in the past. But the world
has progressed, and this approach is no longer favored.
There have been two other instances where the lack of a ~ftp/private
dir has annoyed maintainers on sourceware, but in both cases we
found usable workarounds.
> I'm going to need somewhere that isn't mirrored to put the dreaded file
> gdb-5.0.tar.gz (well actually gdb-4.18.90.tar.gz, gdb-4.18.91, ....)
> before it gets officially released.
Ah, I would suggest ~ftp/pub/gdb/snapshots/gdb-4.18.9[0-9].tar.gz.
Or when you get really close, ~ftp/pub/gdb/snapshots/gdb-5.0pre1.tar.gz.
What purpose does a private dir serve? We've been putting snapshots up
in /pub/ for years, how is a snapshot worse? About the only thing you
need to avoid is putting something called "gdb-5.0.tar.gz" on the ftp
dir that isn't really the final tarball. But you'd be foolish to do
something like that even to a private dir.
Free the Software,
Jason
WARNING: multiple messages have this Message-ID
From: Jason Molenda <jason-swarelist@molenda.com>
To: Andrew Cagney <ac131313@cygnus.com>
Cc: overseers <overseers@sourceware.cygnus.com>
Subject: Re: ~ftp/private/...
Date: Wed, 26 Apr 2000 01:31:00 -0000 [thread overview]
Message-ID: <20000426013124.A4866@shell17.ba.best.com> (raw)
Message-ID: <20000426013100.HiujTob0pXpV0HZqVBr_gpVNpwX23HAMGV82z109k88@z> (raw)
In-Reply-To: <3906A5F0.8535485F@cygnus.com>
On Wed, Apr 26, 2000 at 06:16:48PM +1000, Andrew Cagney wrote:
> Anyone object to me creating a ~ftp/private (/gdb) directory?
Oh oh, Mr. Carter! Me, me!
I set up sourceware without a ~ftp/private on purpose. It is easy
for maintainers or core developers to put things in private
directories needlessly, to cut themselves off from potential
contributors and muckers-at-large (who knows what those random net
people might do!) The lack of a ~ftp/private dir is not an oversight.
It's the approach we took at Cygnus for a long time[1]. It is the
wrong approach. So I didn't create a ~ftp/private dir on sourceware
to help break people of these habits.
[1] To be fair, everyone did it this way in the past. But the world
has progressed, and this approach is no longer favored.
There have been two other instances where the lack of a ~ftp/private
dir has annoyed maintainers on sourceware, but in both cases we
found usable workarounds.
> I'm going to need somewhere that isn't mirrored to put the dreaded file
> gdb-5.0.tar.gz (well actually gdb-4.18.90.tar.gz, gdb-4.18.91, ....)
> before it gets officially released.
Ah, I would suggest ~ftp/pub/gdb/snapshots/gdb-4.18.9[0-9].tar.gz.
Or when you get really close, ~ftp/pub/gdb/snapshots/gdb-5.0pre1.tar.gz.
What purpose does a private dir serve? We've been putting snapshots up
in /pub/ for years, how is a snapshot worse? About the only thing you
need to avoid is putting something called "gdb-5.0.tar.gz" on the ftp
dir that isn't really the final tarball. But you'd be foolish to do
something like that even to a private dir.
Free the Software,
Jason
next prev parent reply other threads:[~2000-12-30 6:08 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2000-12-30 6:08 ~ftp/private/ Andrew Cagney
2000-04-26 1:17 ` ~ftp/private/ Andrew Cagney
2000-12-30 6:08 ` Jason Molenda [this message]
2000-04-26 1:31 ` ~ftp/private/ Jason Molenda
2000-12-30 6:08 ` ~ftp/private/ Andrew Cagney
2000-04-26 2:15 ` ~ftp/private/ Andrew Cagney
2000-12-30 6:08 ` ~ftp/private/ Stan Shebs
2000-04-26 7:24 ` ~ftp/private/ Stan Shebs
2000-12-30 6:08 ` ~ftp/private/ Jason Molenda
2000-04-26 10:16 ` ~ftp/private/ Jason Molenda
2000-12-30 6:08 ` ~ftp/private/ Jim Kingdon
2000-04-28 11:27 ` ~ftp/private/ Jim Kingdon
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=20000426013124.A4866@shell17.ba.best.com \
--to=jason-swarelist@molenda.com \
--cc=ac131313@cygnus.com \
--cc=overseers@sourceware.cygnus.com \
/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).