public inbox for gentoo-dev@lists.gentoo.org
 help / color / mirror / Atom feed
From: Ciaran McCreesh <ciaran.mccreesh@blueyonder.co.uk>
To: gentoo-dev@lists.gentoo.org
Subject: Re: [gentoo-dev] eselect_zenity: alpha eselect GUI
Date: Thu, 8 Nov 2007 12:43:33 +0000	[thread overview]
Message-ID: <20071108124333.2a3dfdc7@blueyonder.co.uk> (raw)
In-Reply-To: <20071108120742.GK5516@supernova>

[-- Attachment #1: Type: text/plain, Size: 1266 bytes --]

On Thu, 8 Nov 2007 04:07:42 -0800
Donnie Berkholz <dberkholz@gentoo.org> 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

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 189 bytes --]

  reply	other threads:[~2007-11-08 12:46 UTC|newest]

Thread overview: 21+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-11-08 10:48 [gentoo-dev] eselect_zenity: alpha eselect GUI Donnie Berkholz
2007-11-08 10:54 ` Ciaran McCreesh
2007-11-08 12:07   ` Donnie Berkholz
2007-11-08 12:43     ` Ciaran McCreesh [this message]
2007-11-08 18:22       ` [gentoo-dev] " Steve Long
2007-11-08 18:34         ` Ciaran McCreesh
2007-11-11  9:43           ` [gentoo-dev] " Steve Long
2007-11-11 11:58             ` [gentoo-dev] " Christian Faulhammer
2007-11-11 13:08             ` [gentoo-dev] " Ciaran McCreesh
2007-11-12  9:13               ` [gentoo-dev] " Steve Long
2007-11-12 13:30                 ` Fernando J. Pereda
2007-11-12 23:30                 ` Jan Kundrát
2007-11-13 15:41                 ` Ciaran McCreesh
2007-11-13 16:13                   ` Dan
2007-11-13 16:22                     ` Jeroen Roovers
2007-11-08 15:03 ` [gentoo-dev] " Luis Francisco Araujo
2007-11-13 19:12 ` Doug Klima
2007-11-13 19:22   ` [gentoo-dev] " Markus Ullmann
2007-11-13 22:07     ` Doug Klima
2007-11-13 22:32     ` Donnie Berkholz
2007-11-13 22:55       ` Rémi Cardona

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20071108124333.2a3dfdc7@blueyonder.co.uk \
    --to=ciaran.mccreesh@blueyonder.co.uk \
    --cc=gentoo-dev@lists.gentoo.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox