public inbox for gentoo-dev@lists.gentoo.org
 help / color / mirror / Atom feed
From: Mike Frysinger <vapier@gentoo.org>
To: gentoo-dev@lists.gentoo.org
Cc: linux.gentoo.dev@googlegroups.com
Subject: Re: [gentoo-dev] Six month major project on Gentoo
Date: Thu, 15 Dec 2011 07:27:43 -0500	[thread overview]
Message-ID: <201112150727.44045.vapier@gentoo.org> (raw)
In-Reply-To: <CADqQcK6kf5=vVJ-BayTDH3WS-HFRgLQ-8HTnfdnYfHLFFTZpWQ@mail.gmail.com>

[-- Attachment #1: Type: Text/Plain, Size: 1538 bytes --]

On Thursday 15 December 2011 00:39:44 Nirbheek Chauhan wrote:
> On Thu, Dec 15, 2011 at 5:28 AM, Mike Frysinger <vapier@gentoo.org> wrote:
> > On Wednesday 14 December 2011 18:43:33 Alec Warner wrote:
> >> On Wed, Dec 14, 2011 at 1:25 PM, Leho Kraav <leho@kraav.com> wrote:
> >> > i'd be really happy if someone took care of
> >> > https://bugs.gentoo.org/150031 :>
> >> > 
> >> > "include more info about binpkg in file name"
> >> 
> >> That is great, but its not a 6 month project...
> > 
> > is it though ?  i'm inclined to mark INVALID.  hijacking filenames for
> > metadata is a tuuuuuuuuuuurrible idea.
> 
> I agree. It's along the same lines as only using file extensions for
> determining the filetype (and we all know how that turned out...). It
> *does* have the advantage of being really fast, though.

it just doesn't scale though (encoding all metadata into the filename quickly 
hits filesystem limits on name length), and i think the speed increase is only 
to a limit.  once you get into larger repos, using the already existing 
"Packages" file would be faster.  and since that compresses, it should scale a 
lot nicer.

> Nevertheless, the basic bug is about changing the distfile repository
> format in such a way that a single repo can contain several distfiles
> built with differing build conditions. Putting metadata in the
> filename is only one way of ensuring that.

sounds like the summary needs updating then by someone who has waded through 
all the followup comments ;)
-mike

[-- Attachment #2: This is a digitally signed message part. --]
[-- Type: application/pgp-signature, Size: 836 bytes --]

  reply	other threads:[~2011-12-15 12:28 UTC|newest]

Thread overview: 26+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <i7USJ-40Q-3@gated-at.bofh.it>
2011-12-14 21:25 ` [gentoo-dev] Six month major project on Gentoo Leho Kraav
2011-12-14 23:43   ` Alec Warner
2011-12-14 23:58     ` Mike Frysinger
2011-12-15  5:39       ` Nirbheek Chauhan
2011-12-15 12:27         ` Mike Frysinger [this message]
2011-12-15 12:42           ` Nirbheek Chauhan
2011-12-15 12:43         ` Rich Freeman
2011-12-15 16:30           ` Mike Frysinger
2011-12-15 16:51             ` Mike Frysinger
2011-12-14 11:06 Gaurav Saxena
2011-12-14 18:05 ` Christian Ruppert
2011-12-14 18:14   ` "C. Bergström"
2011-12-15 18:07   ` Gaurav Saxena
2011-12-19 17:46     ` Christian Ruppert
2011-12-14 18:29 ` Alec Warner
2011-12-15 18:09   ` Gaurav Saxena
2011-12-22  4:43   ` Donnie Berkholz
2011-12-22 10:52     ` Rich Freeman
2011-12-22 11:11       ` Francesco Riosa
2011-12-22 15:55         ` Michał Górny
2011-12-22 16:09           ` Rich Freeman
2011-12-18 17:02 ` Petteri Räty
2011-12-18 17:13   ` "Paweł Hajdan, Jr."
2011-12-18 17:45     ` Michał Górny
2011-12-19 18:14 ` Sébastien Fabbro
2012-01-02 14:33   ` "Paweł Hajdan, Jr."

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=201112150727.44045.vapier@gentoo.org \
    --to=vapier@gentoo.org \
    --cc=gentoo-dev@lists.gentoo.org \
    --cc=linux.gentoo.dev@googlegroups.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