Gentoo Archives: gentoo-guis

From: "René 'Necoro' Neumann" <lists@××××××.eu>
To: gentoo-guis@l.g.o
Subject: Re: [gentoo-guis] One backend for alle portage GUIs
Date: Mon, 22 Oct 2007 16:44:33
In Reply to: [gentoo-guis] One backend for alle portage GUIs by "René 'Necoro' Neumann"
Hash: SHA1

Ok ... some new points =):

1.) The dbus daemon is running the whole time the system is up, when
started once. Therefore the settings should be reloaded each time a
config file (/etc/portage/*, /etc/make.conf ...) is changed. I thought
of using inotify for this issue. Unfortunately, a well known editor
creates some problems: ViM (and I guess other editors behave similary):
It messes around and creates swap-files, temporary files - and instead
of modifying a file directly, it first moves it, then creates a new
modified one and finally deletes the old one (thus the inotify-watch is
gone afterwards).
The creation of the swap files is an issue, when watching a directory
for changes (e.g. /etc/portage). As the files are created _always_, the
settings would be reloaded even if the user only reads the files (and
another time, when he closes it, as the swap files are deleted). This is
definitly a non-optimal solution.

2.) If noone objects in the following days, I would like to write to the
portage-dev-ml about this project (or better: the plans of the project)
and perhaps get some proposals from this side :)

3.) As it is quite some work to maintain two versions of the
portage-backend, I plan to use catapult in Portato by default. But this
depends on how soon we find a solution for 1.).

- -- Necoro
Version: GnuPG v1.4.7 (GNU/Linux)
Comment: Using GnuPG with Mozilla -

gentoo-guis@g.o mailing list


Subject Author
Re: [gentoo-guis] One backend for alle portage GUIs "René 'Necoro' Neumann" <lists@××××××.eu>