public inbox for gentoo-portage-dev@lists.gentoo.org
 help / color / mirror / Atom feed
From: Zac Medico <zmedico@gentoo.org>
To: gentoo-portage-dev@lists.gentoo.org
Subject: Re: [gentoo-portage-dev] [RFC] New file layout for PKGDIR and binhosts
Date: Wed, 24 Dec 2014 08:07:32 -0800	[thread overview]
Message-ID: <549AE4C4.3080306@gentoo.org> (raw)
In-Reply-To: <549AAB08.2050908@gmail.com>

On 12/24/2014 04:01 AM, vivo75@gmail.com wrote:
> Il 24/12/2014 09:13, Zac Medico ha scritto:
>>> I like this (and it has been a long time coming).  What format are we
>>>> going to store the metadata of the use flag combinations and the rest?
>> The current approach is to store the data in an xpak segment that is
>> appended to the end of the tbz2 file. The $PKGDIR/Packages files serves
>> as a cache for the essential parts of the xpak data that are used in
>> dependency calculations.
>>
> I'd like to see the xpak data being put in it's own file at the
> _beginning_ of the tar file.
> 
> tar -Jcf \
>  ${PKGDIR}/${CATEGORY}/${PN}/${PF}-${COUNTER}.xpak \
>  tmp/${CATEGORY}:${PN}:${PF}-${COUNTER}.xpak \
>  *all_the_other_stuff*
> 
> this way reading it could be faster on some media and filesystem  and it
> would not deviate from the standard tar.

There wouldn't be any benefit, because the data is practically always
read from the $PKGDIR/Packages cache anyway. The cache is generated when
the package is built, and the rate-limiting step there is the building
of the package.

> Being in /tmp/ is only for commodity but the place is debatable.
> Instead the fact it _must_ be the first file it's not, in a sequential
> archive file like tar some things depend on it.

With the current approach, the xpak segment is not part of the tar file.
The tar file is compressed, and the xpak segment is appended to the end
of the resulting bzip2 file.

> seem to be the right time to do the change, since tool need to be
> rewritten anyway, but I'll leave to you analyze  the fallout of this change.

There will be zero benefits from doing that.
-- 
Thanks,
Zac


  reply	other threads:[~2014-12-24 16:07 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-12-24  1:51 [gentoo-portage-dev] [RFC] New file layout for PKGDIR and binhosts Zac Medico
2014-12-24  5:16 ` Matthew Thode
2014-12-24  8:13   ` Zac Medico
2014-12-24 12:01     ` vivo75
2014-12-24 16:07       ` Zac Medico [this message]
2014-12-24 18:36         ` vivo75
2014-12-24 19:17           ` Zac Medico
2014-12-25 10:03     ` [gentoo-portage-dev] " Duncan
2014-12-25 11:04       ` Zac Medico
2014-12-26  5:20         ` Duncan
2015-01-07  5:32       ` Brian Dolbec
2014-12-27 14:25 ` [gentoo-portage-dev] " Rick "Zero_Chaos" Farina
2014-12-29  3:53   ` Zac Medico

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=549AE4C4.3080306@gentoo.org \
    --to=zmedico@gentoo.org \
    --cc=gentoo-portage-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