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 11:30:46 -0500	[thread overview]
Message-ID: <201112151130.47143.vapier@gentoo.org> (raw)
In-Reply-To: <CAGfcS_njthbFW-Sn0HgHxe5U9_y-6eR8=q5gaCkV17+Vpupu6g@mail.gmail.com>

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

On Thursday 15 December 2011 07:43:26 Rich Freeman wrote:
> On Thu, Dec 15, 2011 at 12:39 AM, Nirbheek Chauhan wrote:
> > 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.
> 
> Well, having the filename vary when the metadata changes is the only
> way of ensuring that.  Putting the metadata in the filename is just
> one of many ways to make the filename vary.

there is more raw metadata available than fits into a filename.  so that is 
already a non-starter.

if people want to post multiple binpkgs with different metadata

> Another solution (which I can already sense the objections to), would
> be to content-hash the files and use that as the filename.  Then use
> indexes to point to the files.  You could use symlink indexes to point
> to the files so that superficially it looks the same as it does now
> for the last version emerged.  Then people looking for a particular
> set of metadata could use more detailed indexes to find the right
> file.  Portage could look for an exact match when trying to merge a
> binpkg since searching indexes is a trivial problem.

we already hash all the files (i.e. the CONTENTS file), so using the hash of 
that file alone wouldn't be a bad idea.  although i think that file gets 
generated on the fly when merging the binpkg (seems like a waste to not cache 
that in the binary package ...).

> There are countless variations on this as well - like sticking a copy
> of the environment for each package in a separate text file with the
> same base name so that it is easy to grep/search/etc.

the env is already "trivial" to extract:
	qtbz2 -x -O bison-2.5.tbz2 | qxpak -O -x - environment.bz2 | bzgrep foo

> You can also make it more user-friendly by keeping the PF in the
> filename followed by the hash - like gvim-1.23-r1-723ba298d92f.  In
> such a case you probably don't even need to index the PFs.

portage should be using the generated "Packages" index to look up actual tbz2 
filenames, so having ${PF}-<hash>.tbz2 shouldn't be too painful.
-mike

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

  reply	other threads:[~2011-12-15 16:31 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
2011-12-15 12:42           ` Nirbheek Chauhan
2011-12-15 12:43         ` Rich Freeman
2011-12-15 16:30           ` Mike Frysinger [this message]
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=201112151130.47143.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