public inbox for gentoo-soc@lists.gentoo.org
 help / color / mirror / Atom feed
From: "Александр Берсенев" <bay@hackerdom.ru>
To: gentoo-soc@lists.gentoo.org
Subject: Re: [gentoo-soc] rfc: reducing the time of "Calculating dependencies" phase project.
Date: Sat, 27 Apr 2013 11:29:37 +0600	[thread overview]
Message-ID: <CAPomEdyjBs0F-+=BDgDi=mBwpfwJVVadwhSdZb=jXRSb+T_6_A@mail.gmail.com> (raw)
In-Reply-To: <m3zjwkbzao.fsf@carbon.jhcloos.org>

[-- Attachment #1: Type: text/plain, Size: 1214 bytes --]

The modification date of /usr/portage and overlays dir can be used as a
signal for emerge to drop some caches. In this case the drop cache command
could just do "touch <dir>", and utils, modifying tree(e.g. "ebuild
<ebuild> manifest") could do this operation as well.

Best,
Alexander Bersenev



2013/4/27 James Cloos <cloos@jhcloos.com>

> As someone whe often does edit ebuilds in overlays (very occasionally in
> /usr/portage, too), having to run something to update the cache for said
> overlay is OK.
>
> But it *must* update just the cli-specified overlay(s), w/o having to go
> through and update everything every time it is run.
>
> For comparison, my primary workstation, with several overlays, takes
> several minutes to do a dep.  Even with a hot cache.  Improving that to
> something reasonable is the single most important change portage can get.
>
> Also, if /var/db/pkg is to be cached, the existing /var/db/pkg layout
> should remain as a backup, so that the cache of what is installed can
> be restored easily should it ever get corrupted.  Portage can update
> that cache after updating the /var/db/pkg/ tree.
>
> -JimC
> --
> James Cloos <cloos@jhcloos.com>         OpenPGP: 1024D/ED7DAEA6
>
>

[-- Attachment #2: Type: text/html, Size: 1770 bytes --]

  reply	other threads:[~2013-04-27  5:29 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-04-25 18:58 [gentoo-soc] rfc: reducing the time of "Calculating dependencies" phase project Александр Берсенев
2013-04-26  1:17 ` Zac Medico
2013-04-26 11:43   ` Александр Берсенев
2013-04-26 15:59     ` Zac Medico
2013-04-27  0:19       ` James Cloos
2013-04-27  5:29         ` Александр Берсенев [this message]
2013-04-27 19:23           ` Александр Берсенев

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='CAPomEdyjBs0F-+=BDgDi=mBwpfwJVVadwhSdZb=jXRSb+T_6_A@mail.gmail.com' \
    --to=bay@hackerdom.ru \
    --cc=gentoo-soc@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