Hi,
I forgot to remove /etc/gconf/gconf.xml.defaults in my script and I've removed the debugging lines (echo)
Le mercredi 11 ao�t 2004 � 11:43 +0200, Christian Marillat a �crit :
Hi,
I forgot to remove /etc/gconf/gconf.xml.defaults in my script and I've
removed the debugging lines (echo)
This script is completely stupid, it removes all local customization by
the administrator.
Le mardi 17 ao�t 2004 � 11:51 +0200, Christian Marillat a �crit :
This script is completely stupid, it removes all local customization by
the administrator.
If the administrator wants to change something, this change should be
done in a shemas file. And for that reason a shemas file is a
configuration file and the idea to move these files to /usr/share is
completely stupid.
No. Upstream recommends the sysadmin not to change .schema files, but
rather to use gconftool. Changing the .schema file is likely to make the package break on the next update. Don't assume blindly that this change
was made without consulting upstream.
This script is completely stupid, it removes all local customization by
the administrator.
If the administrator wants to change something, this change should be
done in a shemas file. And for that reason a shemas file is a
configuration file and the idea to move these files to /usr/share is completely stupid.
With gconftool you can only change configuration per user, with shemas
files you can changes configuration for all users, like configuring a
proxy.
Le mardi 17 ao�t 2004 � 12:23 +0200, Christian Marillat a �crit :
With gconftool you can only change configuration per user, with shemas
files you can changes configuration for all users, like configuring a
proxy.
You can also change the configuration for all users using gconftool --
direct on the /etc/gconf/gconf.xml.defaults source.
You can also change the configuration for all users using gconftool -- direct on the /etc/gconf/gconf.xml.defaults source.
And for now we don't have any tool to manage that. i'm not talking about
a shell script, but for a real tool, with a configuration file whom
contains keys and values.
On Tue, 2004-08-17 at 13:21 +0200, Christian Marillat wrote:
You can also change the configuration for all users using gconftool --
direct on the /etc/gconf/gconf.xml.defaults source.
And for now we don't have any tool to manage that. i'm not talking about
a shell script, but for a real tool, with a configuration file whom
contains keys and values.
The GNOME GConf Editor can set default and mandatory values if you have
the appropriate permissions.
On Tue, 2004-08-17 at 13:51 +0200, Christian Marillat wrote:
Of course using gconf-editor to changes 20 values is very usefull. click
click click. Ha shit where is this key ?
This is off-topic. Schema files only set defaults as installed by the packages, administrators manipulate the defaults and mandatory
configuration trees. This is how upstream has designed the
architecture.
However, you have a common use-case where you want to change 20
different keys to the same value? I can't see any other use for
Does gtkalog have a shift-selection on multiple check boxes in the preferences dialog? Maybe I should file a bug if not...
Ross Burton <[email protected]> writes:
This is how you are thinking that upstream should use schemas
files. You have filled a bug to move schemas files in /usr/share. This
is your point of view, not the one of other people.
Ross Burton <[email protected]> writes:
On Tue, 2004-08-17 at 13:51 +0200, Christian Marillat wrote:
Of course using gconf-editor to changes 20 values is very usefull. click >> click click. Ha shit where is this key ?
This is off-topic. Schema files only set defaults as installed by the packages, administrators manipulate the defaults and mandatory configuration trees. This is how upstream has designed the
architecture.
This is how you are thinking that upstream should use schemas
files. You have filled a bug to move schemas files in /usr/share. This
is your point of view, not the one of other people.
On Tue, 2004-08-17 at 14:07 +0200, Christian Marillat wrote:
Ross Burton <[email protected]> writes:
On Tue, 2004-08-17 at 13:51 +0200, Christian Marillat wrote:
Of course using gconf-editor to changes 20 values is very usefull. click >> >> click click. Ha shit where is this key ?
This is off-topic. Schema files only set defaults as installed by the
packages, administrators manipulate the defaults and mandatory
configuration trees. This is how upstream has designed the
architecture.
This is how you are thinking that upstream should use schemas
files. You have filled a bug to move schemas files in /usr/share. This
is your point of view, not the one of other people.
Christian, please, talk with upstream or read the gconf documentation
and then we continue talking.
Upstream want to move also the schemas files out of /etc.
Carlos Perello Marin <[email protected]> writes:
On Tue, 2004-08-17 at 14:07 +0200, Christian Marillat wrote:
Ross Burton <[email protected]> writes:
On Tue, 2004-08-17 at 13:51 +0200, Christian Marillat wrote:
Of course using gconf-editor to changes 20 values is very usefull. click
click click. Ha shit where is this key ?
This is off-topic. Schema files only set defaults as installed by the
packages, administrators manipulate the defaults and mandatory
configuration trees. This is how upstream has designed the
architecture.
This is how you are thinking that upstream should use schemas
files. You have filled a bug to move schemas files in /usr/share. This
is your point of view, not the one of other people.
Christian, please, talk with upstream or read the gconf documentation
and then we continue talking.
Upstream want to move also the schemas files out of /etc.
Well, should I wait to read all the GNOME Team comments ?
Frankly I don't care if schemas files are in /usr/share or in /etc, you really can't imagine how I don't care.
Christian--
Frankly I don't care if schemas files are in /usr/share or in /etc, you really can't imagine how I don't care.
On Tue, 2004-08-17 at 15:18 +0200, Christian Marillat wrote:
Carlos Perello Marin <[email protected]> writes:
On Tue, 2004-08-17 at 14:07 +0200, Christian Marillat wrote:
Ross Burton <[email protected]> writes:
On Tue, 2004-08-17 at 13:51 +0200, Christian Marillat wrote:
Of course using gconf-editor to changes 20 values is very usefull. click
click click. Ha shit where is this key ?
This is off-topic. Schema files only set defaults as installed by the >> >> > packages, administrators manipulate the defaults and mandatory
configuration trees. This is how upstream has designed the
architecture.
This is how you are thinking that upstream should use schemas
files. You have filled a bug to move schemas files in /usr/share. This
is your point of view, not the one of other people.
Christian, please, talk with upstream or read the gconf documentation
and then we continue talking.
Upstream want to move also the schemas files out of /etc.
Well, should I wait to read all the GNOME Team comments ?
No, just read the gconf documentation.
Frankly I don't care if schemas files are in /usr/share or in /etc, you
really can't imagine how I don't care.
Then, please stop comment on things you don't know a word guessing that
the others also don't know anything and let's them work.
Le mardi 17 ao�t 2004 � 15:18 +0200, Christian Marillat a �crit :
Frankly I don't care if schemas files are in /usr/share or in /etc, you
really can't imagine how I don't care.
Nice, so you can stop making noise for nothing in the BTS ?
Sebastien Bacher <[email protected]> writes:
Nice, so you can stop making noise for nothing in the BTS ?
Certainly not wait for my next bug reports. I'm a player.
Le mardi 17 ao�t 2004 � 16:16 +0200, Christian Marillat a �crit :
Sebastien Bacher <[email protected]> writes:
Nice, so you can stop making noise for nothing in the BTS ?
Certainly not wait for my next bug reports. I'm a player.
Ok, so these bug reports are a game and not real ones ... I think you
can play alone, we'll just ignore your bug reports from now.
Sebastien Bacher <[email protected]> writes:
I really want to know why you are replying to bug report who are not concerned. I've started this discussion with josselin not you.
Ignoring bug reports is certainly a bad idea and prove your
intelligence. But do you have one ?
And for now we don't have any tool to manage that. i'm not talking about >> a shell script, but for a real tool, with a configuration file whom
contains keys and values.
The GNOME GConf Editor can set default and mandatory values if you have
the appropriate permissions.
Of course using gconf-editor to changes 20 values is very usefull. click click click. Ha shit where is this key ?
| Sysop: | Keyop |
|---|---|
| Location: | Huddersfield, West Yorkshire, UK |
| Users: | 715 |
| Nodes: | 16 (2 / 14) |
| Uptime: | 44:19:55 |
| Calls: | 12,111 |
| Calls today: | 2 |
| Files: | 15,010 |
| Messages: | 6,518,458 |