public inbox for gentoo-dev@lists.gentoo.org
 help / color / mirror / Atom feed
From: Michael Orlitzky <mjo@gentoo.org>
To: gentoo-dev@lists.gentoo.org
Subject: Re: [gentoo-dev] [pre-GLEP] Split distfile mirror directory structure
Date: Sat, 27 Jan 2018 15:16:05 -0500	[thread overview]
Message-ID: <b34e1002-e5a6-7b39-9021-6bc2595e902f@gentoo.org> (raw)
In-Reply-To: <CAHY5Mec2h2=bYYczzLR2QptCKytvGoM8bHk2WzqMnXMe49+Uyw@mail.gmail.com>

On 01/27/2018 02:01 PM, Gordon Pettey wrote:
> On Sat, Jan 27, 2018 at 10:48 AM, Michael Orlitzky <mjo@gentoo.org> wrote:
>> On 01/27/2018 11:42 AM, Gordon Pettey wrote:
>>> Why not use a hash of the file name instead of its contents?...
>>
>> That's the proposal =P
> 
> I'm not following, then. What's all this about a temporary directory
> because of not knowing the hash in advance? The ebuild must specify
> the file name, or src_unpack wouldn't work. There is never a point
> where the file name, and therefore its hash, is unknown.
> 

There were three proposed ways to split up the files: by filename,
hash(filename), and hash(filedata). The winner was hash(filename). The
GLEP lists only two reasons for rejecting hash(filedata), and I was
curious about them.


  reply	other threads:[~2018-01-27 20:16 UTC|newest]

Thread overview: 44+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-01-26 23:24 [gentoo-dev] [pre-GLEP] Split distfile mirror directory structure Michał Górny
2018-01-27  1:48 ` Michael Orlitzky
2018-01-27  2:44   ` R0b0t1
2018-01-27  8:30   ` Michał Górny
2018-01-27 11:36     ` Roy Bamford
2018-01-27 11:41       ` Michał Górny
2018-01-27 16:42         ` Gordon Pettey
2018-01-27 16:48           ` Michael Orlitzky
2018-01-27 19:01             ` Gordon Pettey
2018-01-27 20:16               ` Michael Orlitzky [this message]
2018-01-30  1:21         ` Kent Fredric
2018-01-30  2:53           ` Robin H. Johnson
2018-01-30  7:25           ` Michał Górny
2018-01-30 19:46             ` Kent Fredric
2018-01-27 16:47     ` Michael Orlitzky
2018-01-27 18:14       ` Michał Górny
2018-01-27 18:24         ` Michael Orlitzky
2018-01-27 19:47           ` Michał Górny
2018-01-27 20:30             ` Michael Orlitzky
2018-01-30  1:27           ` Kent Fredric
2018-01-30  7:17             ` Ulrich Mueller
2018-01-28  7:01 ` Jason Zaman
2018-01-28  9:10   ` Michał Górny
2018-01-29  7:33   ` Robin H. Johnson
2018-01-28 10:14 ` Ulrich Mueller
2018-01-28 10:16   ` Michał Górny
2018-01-28 10:22     ` Ulrich Mueller
2018-01-28 10:40       ` Michał Górny
2018-01-28 13:03         ` Ulrich Mueller
2018-01-30  1:41           ` Kent Fredric
2018-01-30  7:11             ` Ulrich Mueller
2018-01-28 20:43 ` Andrew Barchuk
2018-01-28 21:17   ` Gordon Pettey
2018-01-28 22:00     ` Andrew Barchuk
2018-01-28 22:13       ` Gordon Pettey
2018-01-28 22:14       ` Zac Medico
2018-01-28 22:46         ` Andrew Barchuk
2018-01-29  5:36   ` Michał Górny
2018-01-29  9:22     ` Andrew Barchuk
2018-01-29 19:37 ` [gentoo-dev] [pre-GLEP] Split distfile mirror directory structure (draft v2) Michał Górny
2018-01-29 20:00   ` Robin H. Johnson
2018-01-29 21:09     ` Michał Górny
2018-01-29 20:26   ` R0b0t1
2018-01-29 20:55     ` Alec Warner

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=b34e1002-e5a6-7b39-9021-6bc2595e902f@gentoo.org \
    --to=mjo@gentoo.org \
    --cc=gentoo-dev@lists.gentoo.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