On Mon, 21 Aug 2006 00:34:08 +0200, Hisham Muhammad <[EMAIL PROTECTED]>
wrote:
On 8/20/06, Lucas C. Villa Real <[EMAIL PROTECTED]> wrote:
If that fails, there's "sandbox_options=("--no-sandbox")', which will
blindly let that pass.
If anything I'd prefer "sandbox_options=("--add-allowed
${gconf_settings_path}/gconf/gconf.xml.defaults")", which is a bit more
strict.
...and have it break with upgrades, create 'unpackable' /Programs
entries, etc etc. (It never hurts to reiterate those warnings) We need
to find out how appliciations find GConf during configure time and fix
that at once, so that the same solution can be applied to every
gconf-enabled app.
The problem, as I see it, is that apps that wants to write to gconf, wants
to update the xml files, not create own files, so the gconf files have to
exist (or at least links to them) in the dir where the app wants to write.
Possible sollution (rambling):
The app can be configured with "--with-gconf-schema-file-dir=", to have it
try to write it's updates to any directory, so placement isn't an issue.
For updating files, one could make an option to have a copy of the gconf
schemas where the app is configured to write, i.e. /P/App/Settings, then
make a diff with the original files and place that in the
Resources/Defaults/Settings directory. This can later be merged with the
original files with UpdateSettings. But then /P/App/Settings/gconf has to
be a link to the original files, so that UpdateSettings updates the
original files, alternativly a copy of the original files, which
overwrites (symlinked) the latter at /System/Settings.
The issue is that files need to be updated, not overwritten. Probably
manageable in unionsandbox, but in fibosandbox?
--
/Jonas
Using Opera's revolutionary e-mail client: http://www.opera.com/mail/
_______________________________________________
gobolinux-devel mailing list
gobolinux-devel@lists.gobolinux.org
http://lists.gobolinux.org/mailman/listinfo/gobolinux-devel
