[gentoo-portage-dev] refreshing portage

[gentoo-portage-dev] refreshing portage

[Brian]

I have a question.   One of porthole's contributors submitted 2 modules
that can run independant of porthole, but could be used as plugin
modules.  One is a use flag editor and one a features editor, both gtk. 
Doing some testing, it seems that the imported portage & modules used in
porthole are not refreshed after a change in /etc/make.conf..  A spawned
emerge call does see the changes.  The only way I have found for
porthole to see the changes is to close and restart it.

Is there a simple method/function call to reset portage to use the new
changes.
-- 
Brian <dol-sen@telus.net>


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

Re: [gentoo-portage-dev] refreshing portage

[Jason Stubbs]

On Friday 17 September 2004 08:02, Brian wrote:
> I have a question.   One of porthole's contributors submitted 2 modules
> that can run independant of porthole, but could be used as plugin
> modules.  One is a use flag editor and one a features editor, both gtk.
> Doing some testing, it seems that the imported portage & modules used in
> porthole are not refreshed after a change in /etc/make.conf..  A spawned
> emerge call does see the changes.  The only way I have found for
> porthole to see the changes is to close and restart it.
>
> 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

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

Re: [gentoo-portage-dev] refreshing portage

[Brian]

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

Re: [gentoo-portage-dev] refreshing portage

[Marius Mauch]

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

On 09/16/04  Brian wrote:

> I have a question.   One of porthole's contributors submitted 2
> modules that can run independant of porthole, but could be used as
> plugin modules.  One is a use flag editor and one a features editor,
> both gtk. Doing some testing, it seems that the imported portage &
> modules used in porthole are not refreshed after a change in
> /etc/make.conf..  A spawned emerge call does see the changes.  The
> only way I have found for porthole to see the changes is to close and
> restart it.
> 
> Is there a simple method/function call to reset portage to use the new
> changes.

Does `reload(portage)` work ?

Marius

[-- Attachment #2: Type: application/pgp-signature, Size: 189 bytes --]