From: Mike Frysinger <vapier@gentoo.org>
To: Doug Goldstein <cardoe@gentoo.org>
Cc: gentoo-dev@lists.gentoo.org, Roy Marples <roy@marples.name>
Subject: Re: [gentoo-dev] OpenRC & baselayout-2 meets Gentoo
Date: Tue, 25 Mar 2008 08:30:32 -0400 [thread overview]
Message-ID: <200803250830.33662.vapier@gentoo.org> (raw)
In-Reply-To: <47E83E1A.7040003@gentoo.org>
[-- Attachment #1: Type: text/plain, Size: 1538 bytes --]
On Monday 24 March 2008, Doug Goldstein wrote:
> Mike Frysinger wrote:
> > On Monday 24 March 2008, Doug Goldstein wrote:
> >> /etc/modules.autoload.d has always allowed module parameters to appear
> >> after the module name.
> >>
> >> /etc/conf.d/modules has allowed a completely different syntax requiring
> >> variables based on the module name to be set with the module parameters.
> >>
> >> This is where Roy and I have been stuck as far as an automatic
> >> conversion process. The stuff you included in the openrc-9999 ebuild was
> >> something I had sent to Roy months ago before I realized module
> >> parameters would be an issue. Looking at a swath of various
> >> /etc/modules.autoload.d/ files, I haven't come up with shell code that
> >> does the right thing everytime with all the files, which is why I've
> >> left it up to being a manual process for the user and simply documenting
> >> it.
> >
> > expecting users to read and do it themselves is certainly a path to
> > destruction for many. while i could have written it in shell, i just did
> > it in awk. i hope you're just overstating things when you say months,
> > because FIXED:INCVS.
> >
> > we're going to need to extend the syntax anyways to allow for
> > per-version-per-module arguments. unless openrc does that now ... Roy ?
>
> Currently OpenRC does not support per-version-per-module arguments. What
> is your proposed syntax?
i'd assume logically extended based on existing behavior. Roy's done it now
though.
-mike
[-- Attachment #2: This is a digitally signed message part. --]
[-- Type: application/pgp-signature, Size: 827 bytes --]
next prev parent reply other threads:[~2008-03-25 12:27 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-03-20 5:19 [gentoo-dev] OpenRC & baselayout-2 meets Gentoo Doug Goldstein
2008-03-20 6:59 ` Josh Saddler
2008-03-20 12:12 ` Roy Marples
2008-03-20 14:16 ` Doug Goldstein
2008-03-20 14:34 ` Daniel Pielmeier
2008-03-20 20:13 ` [gentoo-dev] Re: [gentoo-core] " Mike Frysinger
2008-03-24 20:26 ` [gentoo-dev] " Doug Goldstein
2008-03-24 20:35 ` Josh Saddler
2008-03-24 20:47 ` Doug Goldstein
2008-03-24 21:08 ` [gentoo-core] " Mike Frysinger
2008-03-24 21:16 ` Doug Goldstein
2008-03-24 21:32 ` Mike Frysinger
2008-03-24 21:36 ` Doug Goldstein
2008-03-24 21:42 ` Mike Frysinger
2008-03-24 21:53 ` Doug Goldstein
2008-03-24 22:03 ` Mike Frysinger
2008-03-24 23:49 ` Doug Goldstein
2008-03-25 12:30 ` Mike Frysinger [this message]
2008-03-25 8:33 ` Roy Marples
2008-03-25 12:29 ` Mike Frysinger
2008-03-27 14:57 ` Doug Goldstein
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=200803250830.33662.vapier@gentoo.org \
--to=vapier@gentoo.org \
--cc=cardoe@gentoo.org \
--cc=gentoo-dev@lists.gentoo.org \
--cc=roy@marples.name \
/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