Re: [gentoo-dev] eselect_zenity: alpha eselect GUI
Donnie Berkholz wrote: > Hey all, > > I've been wanting a GUI for eselect lately, so tonight I hacked up the > start of one called eselect_zenity [1]. It only works for the most > trivial modules so far -- it has to parse eselect output, so special > parsers need to be written for each type. eselect_zenity uses > (surprise!) Zenity, a shell-scripting interface to GTK+. > > I'd appreciate any patches you'd like to contribute to add functionality > or fix bugs. > > Thanks, > Donnie > > 1. http://dev.gentoo.org/~dberkholz/eselect_zenity/ > This is something really good. I've been thinking that Gentoo could use a few small GUI utilities. Items such as a notification-applet for GLSA bits that affect your system. Similiar to Ubuntu's tool when there's updates that need to be applied. Additionally, I'd like to see all these utilities wrapped via PolicyKit rather then using gksu and kdesu applications. PolicyKit is definitely the way forward on designing custom, granular permissions and not relying on root in a GUI environment. While I haven't had much time to work on the bits, Gentopia does contain PolicyKit (though the 0.7 snapshots that appear do have some issues and you should stick to the 0.6 series). It's hopefully going to be the way forward for Gentoo to use PolicyKit. As many may know, Fedora has made this commitment and Ubuntu is starting to contribute more back and be involved a bit more. -- [EMAIL PROTECTED] mailing list
Re: [gentoo-dev] eselect_zenity: alpha eselect GUI
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Donnie Berkholz wrote: > Hey all, > > I've been wanting a GUI for eselect lately, so tonight I hacked up the > start of one called eselect_zenity [1]. It only works for the most > trivial modules so far -- it has to parse eselect output, so special > parsers need to be written for each type. eselect_zenity uses > (surprise!) Zenity, a shell-scripting interface to GTK+. > > I'd appreciate any patches you'd like to contribute to add functionality > or fix bugs. > > Thanks, > Donnie > > 1. http://dev.gentoo.org/~dberkholz/eselect_zenity/ Nice work, you should announce it too at the gentoo-guis ml. :-) Regards, - -- Luis F. Araujo "araujo at gentoo.org" Gentoo Linux -BEGIN PGP SIGNATURE- Version: GnuPG v2.0.7 (GNU/Linux) iD8DBQFHMyVKBCmRZan6aegRAq51AKDGK606Kms7RR06mR0uGD95NtEvRgCeL+Rk UX948bV08q/nN5ryBVt8dlg= =XVMM -END PGP SIGNATURE- -- [EMAIL PROTECTED] mailing list
Re: [gentoo-dev] eselect_zenity: alpha eselect GUI
On Thu, 8 Nov 2007 04:07:42 -0800
Donnie Berkholz <[EMAIL PROTECTED]> wrote:
> I'll look into that. Got any good starting points (files, functions,
> docs)?
Well, the whole of the eselect code is small enough that you should be
able to understand it pretty quickly... Then it'd just be a case of
making the main driver code a bit more flexible so that you can tell it
to swap in certain libraries.
Incidentally, I suspect it might be worth rewriting the core using some
of the techniques that we've discovered when writing Paludis. Things
like the fancier signalling die function and the cleaner module path
searching would be worth adopting. This would also be a good
opportunity to sneak in the more flexible driver that you probably
need. Might be worth speaking to whoever maintains Gentoo's branch of
eselect these days.
One thing in the code, by the way...
if [[ ${UID} -ne 0 ]]; then
We've always told people not to do that. Capabilities required by
eselect modules should be tested by attempting to perform the action,
not by some arbitrary query done on UIDs or groups. Being UID 0 doesn't
mean you're allowed to do something, and not being UID 0 doesn't mean
you're not allowed to do something.
--
Ciaran McCreesh
signature.asc
Description: PGP signature
Re: [gentoo-dev] eselect_zenity: alpha eselect GUI
On 10:54 Thu 08 Nov , Ciaran McCreesh wrote: > On Thu, 8 Nov 2007 02:48:13 -0800 > Donnie Berkholz <[EMAIL PROTECTED]> wrote: > > it has to parse eselect output > > Part of the idea behind using standardised output functions was that > they could be replaced. The thought was, rather than trying to parse > console-centric output, you'd swap in a different implementation of the > output functions that fed to, say, ncurses or a GUI. Then you'd swap > the driver logic with something that calls multiple tasks in order > rather than merely doing one thing and then exiting (there's proper > environment isolation to allow that). > > Might be easier to do things that way... I'll look into that. Got any good starting points (files, functions, docs)? Thanks, Donnie -- [EMAIL PROTECTED] mailing list
Re: [gentoo-dev] eselect_zenity: alpha eselect GUI
On Thu, 8 Nov 2007 02:48:13 -0800 Donnie Berkholz <[EMAIL PROTECTED]> wrote: > it has to parse eselect output Part of the idea behind using standardised output functions was that they could be replaced. The thought was, rather than trying to parse console-centric output, you'd swap in a different implementation of the output functions that fed to, say, ncurses or a GUI. Then you'd swap the driver logic with something that calls multiple tasks in order rather than merely doing one thing and then exiting (there's proper environment isolation to allow that). Might be easier to do things that way... -- Ciaran McCreesh signature.asc Description: PGP signature
