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 62C961381F4 for ; Fri, 17 Aug 2012 02:03:21 +0000 (UTC) Received: from pigeon.gentoo.org (localhost [127.0.0.1]) by pigeon.gentoo.org (Postfix) with SMTP id 4AE7621C008; Fri, 17 Aug 2012 02:03:01 +0000 (UTC) Received: from mail-bk0-f53.google.com (mail-bk0-f53.google.com [209.85.214.53]) by pigeon.gentoo.org (Postfix) with ESMTP id 431EFE05ED for ; Fri, 17 Aug 2012 02:02:16 +0000 (UTC) Received: by bkwj4 with SMTP id j4so1433643bkw.40 for ; Thu, 16 Aug 2012 19:02:16 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :content-type; bh=gRf/zB+nUO59w83AiExEP5rpE//zDd7OzVEXfJctNWQ=; b=FJ/XL+DTp1jET5lh0QDGClEfb5slaY8lLMJCoQLnAbp+NrWQSm78upU+CiUkxCoiZo oBJh4HY/xZJDDE/DdKY560Z6FTKzUF/H9ly3kJeV99iqaIrPSFQJvBpw9DYWUfoEwlJv /8+UGFe6YHZ06dZbm7wAByk4pP+7gbaObi5tOfS3kjzxRgnbed7+Vi55KMLjN9qmTrmU 6p9UrhTqQsV4qmUT+jf3i1lncCe1MMClQf/Jf4ICNKs4evKNas2AO3SbZs6TK7e1cSmr Jfmqcj9AXmgwPRrQwPWN7gF/fOCO05C4JdiQAnqbHpc/dcKW7zRQrWjbiuBfpwClOVRk 1UDQ== Precedence: bulk List-Post: List-Help: List-Unsubscribe: List-Subscribe: List-Id: Gentoo Linux mail X-BeenThere: gentoo-dev@lists.gentoo.org Reply-to: gentoo-dev@lists.gentoo.org MIME-Version: 1.0 Received: by 10.204.136.205 with SMTP id s13mr1350652bkt.22.1345168936119; Thu, 16 Aug 2012 19:02:16 -0700 (PDT) Received: by 10.205.25.8 with HTTP; Thu, 16 Aug 2012 19:02:15 -0700 (PDT) In-Reply-To: References: <1344366029.24762.31.camel@TesterTop4> <502377E7.8010803@gentoo.org> <1344535966.2121.6.camel@TesterTop4> <20120809183130.GA6795@linux1> <20120809195727.5d04ccff@googlemail.com> <20120814032416.GA8489@kroah.com> <502D4F41.9080608@malth.us> Date: Thu, 16 Aug 2012 22:02:15 -0400 Message-ID: Subject: Re: [gentoo-dev] Re: Questions about SystemD and OpenRC From: Michael Mol To: gentoo-dev@lists.gentoo.org Content-Type: text/plain; charset=UTF-8 X-Archives-Salt: 88ee6b02-d1fa-4a5c-b638-cdc43dbd5ec6 X-Archives-Hash: b91191c66fb83cc29cc9e736067dcf83 On Thu, Aug 16, 2012 at 9:26 PM, Rich Freeman wrote: > On Thu, Aug 16, 2012 at 4:05 PM, Michael Mol wrote: >> The limited-visibility build feature discussed a week or so ago would >> go a long way in detecting unexpressed build dependencies. > > I can't say that is a coincidence, but my intent would be to include > @system as implicit dependencies, at least until we change that policy > (though the morbidly curious could use that as a test in a tinderbox > to find packages in @system that are good candidates for removal). > > I haven't gotten to test it, but after studying sandbox it shouldn't > be hard to just hack together a manual test by removing read access to > root from the config files and adding in a bazillion files. That > should at least let me profile performance/etc. I'm not convinced > that there isn't room for improvement, but if it works well as-is then > automating this shouldn't be hard at all. If portage has the > dependency tree in RAM then you just need to dump all the edb listings > for those packages plus @system and feed those into sandbox. That > just requires reading a bunch of text files and no searching, so it > should be pretty quick. As far as I can tell the relevant calls to > check for read access are already being made in sandbox already, and > obviously they aren't taking forever. We just have to see if the > search gets slow if the access list has tens of thousands of entries > (if it does, that is just a simple matter of optimization, but being > in-RAM I can't see how tens of thousands of entries is going to slow > down a modern CPU even if it is just an unsorted list). Yeah, I presumed you'd have @system as a set of implicit dependencies. The obvious approaches would be to either temporarily remove a package from @system, tell the portage to ignore a package while doing limited visibility, or copy @system to a different, temporary set and remove things piecemeal from there. That last might make the most sense. "--implicit-dependencies --- defaults to @system. Additional instances append to the set of implicit dependencies. Use, e.g. -${ATOM} or -@system to override default include." -- :wq