From: "Robin H. Johnson" <robbat2@gentoo.org>
To: gentoo-dev@lists.gentoo.org
Subject: Re: [gentoo-dev] Re: [gentoo-commits] repo/gentoo:master commit in: net-fs/samba/, net-fs/samba/files/, net-fs/samba/files/4.4/
Date: Wed, 10 Feb 2016 05:33:41 +0000 [thread overview]
Message-ID: <robbat2-20160210T052648-883915394Z@orbis-terrarum.net> (raw)
In-Reply-To: <20160210052222.GA10107@meriadoc>
On Wed, Feb 10, 2016 at 01:22:22PM +0800, Jason Zaman wrote:
> We do not need the whole manifest checking, we just need to have a list
> of SRC_URI that is being added in any ebuilds and then grep Manifest if
> those filenames exist. The receive hook checking the hashes of the files
> is probably asking too much. This would miss any files added by eclasses
> but that is rare and changes less often so we should probably be okay.
>
> Is there any sane way to spit out condensed SRC_URI for all use-flags?
eclasses add a LOT.
Of the ~40k ebuilds in the tree, ~11k do not match the regex /^\w*SRC_URI/.
This means that you need an update to date copy of eclasses at the very
least. If Portage/pkgcore could work on a tree that had only a partial
Git checkout of: eclasses/, metadata/, cat/pn/
Then this probably COULD run much faster.
--
Robin Hugh Johnson
Gentoo Linux: Developer, Infrastructure Lead, Foundation Trustee
E-Mail : robbat2@gentoo.org
GnuPG FP : 11ACBA4F 4778E3F6 E4EDF38E B27B944E 34884E85
prev parent reply other threads:[~2016-02-10 5:33 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <1455055580.bedb32a1fbb6675c639446b39d25d4f13e2d4b67.axs@gentoo>
2016-02-09 23:50 ` [gentoo-dev] Re: [gentoo-commits] repo/gentoo:master commit in: net-fs/samba/, net-fs/samba/files/, net-fs/samba/files/4.4/ Robin H. Johnson
2016-02-10 0:03 ` Tim Harder
2016-02-10 0:59 ` Robin H. Johnson
2016-02-10 1:08 ` Tim Harder
2016-02-10 1:24 ` Robin H. Johnson
2016-02-10 5:11 ` Robin H. Johnson
2016-02-10 5:22 ` Jason Zaman
2016-02-10 5:33 ` Robin H. Johnson [this message]
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=robbat2-20160210T052648-883915394Z@orbis-terrarum.net \
--to=robbat2@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