Josselin Mouette wrote:
being repeatedly faced with trouble about the GConf architecture, I've
thought a bit about the global GConf situation, and I'm therefore
proposing some improvements I'd like this to be discussed a bit before
any code comes up. I'll try to summarize the current
Stanislav Brabec wrote:
It's not problem of Debian, but it should be addressed by future
development, too:
--makefile-uninstall-rule is incompatible with packaging systems
http://bugzilla.gnome.org/show_bug.cgi?id=306924
The three fixes I keep mentioning at every opportunity would fix
Hi,
Sorry for the late reply, I hadn't seen Olafur's question until today
since I'm only subscribed to gconf-list.
Is apoc source code anywhere, it seems to be java program but
the project page seems to be an internal website at sun, and
I can't find the files anywhere.
APOC's open
On Sat, 2006-11-11 at 12:02 +0100, Josselin Mouette wrote:
Hi,
being repeatedly faced with trouble about the GConf architecture, I've
thought a bit about the global GConf situation, and I'm therefore
proposing some improvements I'd like this to be discussed a bit before
any code comes up.
Is apoc source code anywhere, it seems to be java program but
the project page seems to be an internal website at sun, and
I can't find the files anywhere.
With java going opensource, it could be a great addition to
the admin section in gnome 2.10, but first it needs some
exposure outside of
Thanks for your answer, it cast light on many of my interrogations.
Le samedi 11 novembre 2006 à 13:18 -0500, Havoc Pennington a écrit :
As a preface to responding to your mail, keep in mind that there are two
interface points that need not use the same mechanism:
user session on a host
Some time ago I did a deployment test for an enterprise-wide migration
to GNOME (around 10,000 hosts), and I found useful some python scripts
to tweak some GConf keys in Evolution, and retrieve data from a LDAP.
From this special case I had to query an Active Directory server to
obtain users data
On Sat, 2006-11-11 at 22:24 +0800, Davyd Madeley wrote:
On Sat, 2006-11-11 at 12:02 +0100, Josselin Mouette wrote:
There are several ways to deal with a single-session, single-host
configuration engine. Real problems arise when the user can log in
several times on different machines, with
Davyd Madeley wrote:
On Sat, 2006-11-11 at 12:02 +0100, Josselin Mouette wrote:
There are several ways to deal with a single-session, single-host
configuration engine. Real problems arise when the user can log in
several times on different machines, with a shared filesystem. With the
Hi,
being repeatedly faced with trouble about the GConf architecture, I've
thought a bit about the global GConf situation, and I'm therefore
proposing some improvements I'd like this to be discussed a bit before
any code comes up. I'll try to summarize the current situation for those
who don't
Josselin Mouette wrote:
To achieve this, the first thing to do - and it should have been done
for a long time - is to move the file notification API from gnome-vfs to
glib.
I enjoin you to look at the GVFS effort on the gnomevfs-list archives.
The idea is basically to write a replacement for
Hi Josselin;
On Sat, 2006-11-11 at 12:02 +0100, Josselin Mouette wrote:
How about forgetting this communication thing? Configuration is stored
in files, we just need to read and write these files. We even have some
decent ways to monitor files now: local using inotify, remote using fam
with
On Sat, Nov 11, 2006, Davyd Madeley wrote:
It is possible to write alternative GConf backends. I recall that Sun
have written one that uses LDAP, its name starts with an A, but I can't
recall what it is.
You don't mean evoldap?
--
Loïc Minier [EMAIL PROTECTED]
On Sat, 2006-11-11 at 12:02 +0100, Josselin Mouette wrote:
There are several ways to deal with a single-session, single-host
configuration engine. Real problems arise when the user can log in
several times on different machines, with a shared filesystem. With the
number of corporate users
Davyd Madeley wrote:
On Sat, 2006-11-11 at 12:02 +0100, Josselin Mouette wrote:
There are several ways to deal with a single-session, single-host
configuration engine. Real problems arise when the user can log in
several times on different machines, with a shared filesystem. With the
Le samedi 11 novembre 2006 à 09:21 -0600, Joe Baker a écrit :
An example of the model of communications needed is the IMAP IDLE
protocol. Clients have the connection opened up and the server polls
the client when there are changes to the mailstore that they should be
aware of. Multiple
Hi,
It's very simple:
http://www.gnome.org/projects/gconf/plans.html
We just need a volunteer to do those *three things* and a whole lot of
pain would go away.
As a preface to responding to your mail, keep in mind that there are two
interface points that need not use the same mechanism:
17 matches
Mail list logo
