From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from lists.gentoo.org (pigeon.gentoo.org [208.92.234.80]) by finch.gentoo.org (Postfix) with ESMTP id 7FDD21389E2 for ; Wed, 24 Dec 2014 16:07:38 +0000 (UTC) Received: from pigeon.gentoo.org (localhost [127.0.0.1]) by pigeon.gentoo.org (Postfix) with SMTP id B2D51E0807; Wed, 24 Dec 2014 16:07:35 +0000 (UTC) Received: from smtp.gentoo.org (smtp.gentoo.org [140.211.166.183]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by pigeon.gentoo.org (Postfix) with ESMTPS id 30662E07F5 for ; Wed, 24 Dec 2014 16:07:35 +0000 (UTC) Received: from [192.168.100.192] (67-203-132-147.static-ip.telepacific.net [67.203.132.147]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) (Authenticated sender: zmedico) by smtp.gentoo.org (Postfix) with ESMTPSA id 41A5E34029D for ; Wed, 24 Dec 2014 16:07:34 +0000 (UTC) Message-ID: <549AE4C4.3080306@gentoo.org> Date: Wed, 24 Dec 2014 08:07:32 -0800 From: Zac Medico User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:31.0) Gecko/20100101 Thunderbird/31.3.0 Precedence: bulk List-Post: List-Help: List-Unsubscribe: List-Subscribe: List-Id: Gentoo Linux mail X-BeenThere: gentoo-portage-dev@lists.gentoo.org Reply-to: gentoo-portage-dev@lists.gentoo.org MIME-Version: 1.0 To: gentoo-portage-dev@lists.gentoo.org Subject: Re: [gentoo-portage-dev] [RFC] New file layout for PKGDIR and binhosts References: <549A1C31.8040500@gentoo.org> <549A4C25.9050000@gentoo.org> <549A75C5.70600@gentoo.org> <549AAB08.2050908@gmail.com> In-Reply-To: <549AAB08.2050908@gmail.com> Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 8bit X-Archives-Salt: 9012471d-6b2b-462a-bf48-789dd6d8cf38 X-Archives-Hash: faa83bb91a3ae077b37b4d9f83c97f46 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