public inbox for gentoo-portage-dev@lists.gentoo.org
 help / color / mirror / Atom feed
From: Brian <dol-sen@telus.net>
To: gentoo-portage-dev <gentoo-portage-dev@lists.gentoo.org>
Subject: Re: [gentoo-portage-dev] refreshing portage
Date: Thu, 16 Sep 2004 18:39:20 -0700	[thread overview]
Message-ID: <1095385160.16413.142.camel@localhost> (raw)
In-Reply-To: <200409170825.18731.jstubbs@gentoo.org>

On Thu, 2004-09-16 at 16:25, Jason Stubbs wrote:
> On Friday 17 September 2004 08:02, Brian wrote:

> > Is there a simple method/function call to reset portage to use the new
> > changes.
> 
> reload(portage)
> 
> Note that this is relatively heavy as everything is reinitialized, so try to 
> do it as little as possible.
> 
> Regards,
> Jason Stubbs
> 
On Thu, 2004-09-16 at 16:30, Marius Mauch wrote:

> Does `reload(portage)` work ?
> 
> Marius
> 

Yes that does the trick.  Thank you.

I didn't know if there was an internal portage module that could reload /etc/make.conf.
It did not seem to slow a reload down too much on my system but I imagine it could for
some of the older slower machines.   Now I'll have to come up with a method for plugins 
to interface with porthole.   Hopefully Dan will be back in operation soon so we can set up
a good plan of attack.


Also, while I've got your attention.   I was experimenting with some things and noticed that 
when I had temporarily renamed /etc/portage/package.keywords, porthole seemed to reload the
upgrades list in less than half the time.   Is there any plan or thoughts to cache the file
(if it isn't already) to speed things up, or is it something unavoidable.
-- 
Brian <dol-sen@telus.net>


--
gentoo-portage-dev@gentoo.org mailing list


  reply	other threads:[~2004-09-17  1:39 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-09-16 23:02 [gentoo-portage-dev] refreshing portage Brian
2004-09-16 23:25 ` Jason Stubbs
2004-09-17  1:39   ` Brian [this message]
2004-09-16 23:30 ` Marius Mauch

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=1095385160.16413.142.camel@localhost \
    --to=dol-sen@telus.net \
    --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