Hi Lennon
On 11/23/05, Lennon Cook <[EMAIL PROTECTED]> wrote:
> Luca Dionisi wrote:
> > If I got it, you mean that any pkg installation that
> > wants to add things to that database will use this program. Right?
> Yes. It works in a similar way to gconf - package provides raw files,
> runs that app to register them in the database. Ofcourse, the
> workaround for gconf is nowhere near as neat (since to register gconf
> schemas, the install scripts use gconftool-2, which is also useful to
> non-package users).
>
Please, confirm if I'm getting right the way these kind of database work:
e.g. I know that if an application wants to add a new MIME-type to the
shared-mime-info db, this application has to install a file in
a particular
location (/usr/share/mime/packages/foobar.xml) and then launch a
tool (update-mime-database) to update one or more files
(/usr/share/mime/globs, ...)
So, I gave to the tool the setuid privileges needed to permit
any pkg-user
to accomplish this task.
Now, since you enlightened me about the presence of similar tools for gconf2,
I would ask:
1- given an installation that wants to save configuration in gconf2 or in the
scrollkeeper database, is the behaviour of that installation similar to the
one I described?
2- If yes, where does the installation put its files before to call
gconftool2 /
scrollkeeper-update ?
I'm going to set the setuid bit for the scrollkeeper-update tool as you
suggested. About gconftool-2, since you said it is used also by normal
users, I'm going to install it normally and then place a copy of it in the
executable path used by the install group and set the suid bit in that copy.
What do you think of this solution? Is it going to work?
Thanks a lot.
Luca
--
http://linuxfromscratch.org/mailman/listinfo/blfs-support
FAQ: http://www.linuxfromscratch.org/blfs/faq.html
Unsubscribe: See the above information page
