Re: Debian archive requirements
- To: firstname.lastname@example.org
- Subject: Re: Debian archive requirements
- From: Rob Browning <email@example.com>
- Date: 06 Nov 1999 12:26:35 -0600
- Message-id: <firstname.lastname@example.org>
- In-reply-to: Adrian Bridgett's message of "Thu, 4 Nov 1999 22:45:38 +0000"
- References: <Pine.LNX.3.96.991018014209.31634A-100000@localhost> <Pine.LNX.3.96.991018105558.2255Aemail@example.com> <19991018183618.A817@verbum.org> <19991018184703.G15774@justice.loyola.edu> <199910301228.NAA32332@paladin.demon.co.uk> <firstname.lastname@example.org> <19991104224538.B3897@wyvern>
Adrian Bridgett <email@example.com> writes:
> 1) I don't want an "ls" over a modem to take 10mins to download so one giant
> directory is a really bad idea.
That's why I said a "hashed" directory tree, though I should have been
> 2) How about using the first character. Here is a rough list of how many
> packages this means per dir - x/ isn't half as bad as I expected, OTOH l/ is
> pretty bad.
Right, when I said a hashed tree, I meant something like that, though
that might not be the exact scheme you want. You could do it on the
first two letters, groups of three or four, etc.
Whatever, and we could still provide a more user friendly ftp tree as
an automatically generated symlink farm from our main repository, for
people who can't, or don't want to, use our tools.
Rob Browning <firstname.lastname@example.org> PGP=E80E0D04F521A094 532B97F5D64E3930