public inbox for gentoo-dev@lists.gentoo.org
 help / color / mirror / Atom feed
From: Steve Long <slong@rathaus.eclipse.co.uk>
To: gentoo-dev@lists.gentoo.org
Subject: [gentoo-dev]  Re: OpenRC available for testing.
Date: Sun, 06 Jan 2008 13:34:49 +0000	[thread overview]
Message-ID: <flql27$ag6$1@ger.gmane.org> (raw)
In-Reply-To: 1199384389.28193.24.camel@localhost

Roy Marples wrote:
> So, the question is, do we want to maintain one massive KV_to_int that
> has different code paths for uname -s output, or get function.sh to
> include an OS specific file we supply just for this one function?
> 
> Or just put the function in modules-update and udev as they are the only
> two applications that use it.
>
I vote for option 1b, if that's how you've decided to implement it. I'd
rather it was just a simple function in the OS-specific function.sh though.

>> if you want a cleaner interface for is_older_than, then we could hammer
>> that out, but if it's just a pass through to a C applet, then leaving it
>> alone makes sense.
> 
> Currently it's neither as it's been integrated into the librc dependency
> code. Again, the only consumer of this function is now modules-update.
> 
OK, but that doesn't mean it won't be needed in the future. It's already
there, it might be handy later, leave it available imho.


-- 
gentoo-dev@lists.gentoo.org mailing list



  reply	other threads:[~2008-01-06 13:29 UTC|newest]

Thread overview: 44+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-01-01 12:41 [gentoo-dev] OpenRC available for testing Roy Marples
2008-01-01 12:45 ` Roy Marples
2008-01-01 13:23   ` Alon Bar-Lev
2008-01-01 15:06     ` Petteri Räty
2008-01-01 16:55       ` Alon Bar-Lev
2008-01-01 17:11         ` Roy Marples
2008-01-01 17:22         ` Alon Bar-Lev
2008-01-01 17:48           ` Roy Marples
2008-01-03  6:43           ` Alon Bar-Lev
2008-01-03  9:46             ` Roy Marples
2008-01-03 10:02               ` Alon Bar-Lev
2008-01-03 10:09                 ` Roy Marples
2008-01-01 19:16 ` Thomas Pani
2008-01-01 19:31   ` TimeBreach
2008-01-01 19:49   ` Roy Marples
2008-01-02 14:39     ` Alon Bar-Lev
2008-01-02 15:05       ` Roy Marples
2008-01-02 15:15         ` Alon Bar-Lev
2008-01-02 15:50           ` Roy Marples
2008-01-03 15:49         ` Mike Frysinger
2008-01-03 18:19           ` Roy Marples
2008-01-06 13:34             ` Steve Long [this message]
2008-01-09 21:26             ` Mike Frysinger
2008-01-09 21:48               ` Chris Gianelloni
2008-01-09 22:58                 ` Mike Frysinger
2008-01-03 15:50     ` Mike Frysinger
2008-01-03 16:24       ` Roy Marples
2008-01-03 17:58         ` Roy Marples
2008-01-09 21:27           ` Mike Frysinger
2008-01-02 16:52 ` Santiago M. Mola
2008-01-02 17:39   ` Roy Marples
2008-01-03  4:38 ` Nathan Smith
2008-01-03  9:49   ` Roy Marples
     [not found] ` <9e0cf0bf0801030055u3564058fy7f9595d4df86674a@mail.gmail.com>
2008-01-03  8:58   ` Alon Bar-Lev
2008-01-03  9:50     ` Roy Marples
2008-01-03 10:13       ` Roy Marples
2008-01-03 10:18         ` Richard Brown
2008-01-03 10:40           ` Roy Marples
2008-01-03 12:12             ` Santiago M. Mola
2008-01-06 13:45               ` [gentoo-dev] " Steve Long
2008-01-03 14:01           ` [gentoo-dev] " Wulf C. Krueger
2008-01-09 21:30             ` Mike Frysinger
2008-01-03 23:35           ` Luca Barbato
2008-01-03 11:43       ` Alon Bar-Lev

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='flql27$ag6$1@ger.gmane.org' \
    --to=slong@rathaus.eclipse.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