From: William Hubbs <williamh@gentoo.org>
To: gentoo-dev@lists.gentoo.org
Subject: Re: [gentoo-dev] systemd profiles
Date: Wed, 3 Sep 2014 13:11:14 -0500 [thread overview]
Message-ID: <20140903181114.GA14334@linux1> (raw)
In-Reply-To: <CAGfcS_npKD2JfKmgj3jJ-ipiA9nOT13YaGMW8N6ze75H1bvhXQ@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 812 bytes --]
On Sat, Aug 30, 2014 at 09:45:23AM -0400, Rich Freeman wrote:
> A possible solution is to remove it in the next version of openrc, as
> it is deprecated already. Another solution is to ask the Council to
> let somebody apply patches if the maintainer is unresponsive, set a
> deadline, etc.
The problem is we have two different API's. Gentoo's API for tools that
do not involve booting, and OpenRC's API. In the past, they were
identical, but that isn't the case now.
That is why I haven't removed /etc/init.d/functions.sh. That is actually
part of OpenRC's public API now.
I can deprecate it. To do so, I would need to have it print out a
deprecation warning that would be wrong for Gentoo in the next release.
That warning would have to tell users to source
/lib*/rc/sh/functions.sh.
Thoughts?
William
[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 181 bytes --]
next prev parent reply other threads:[~2014-09-03 18:11 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-08-29 23:09 [gentoo-dev] systemd profiles Jauhien Piatlicki
2014-08-29 23:27 ` Alex Xu
2014-08-30 2:41 ` Rich Freeman
2014-08-30 9:09 ` Jauhien Piatlicki
2014-08-30 11:27 ` J. Roeleveld
2014-08-30 11:41 ` Michał Górny
2014-08-30 12:03 ` Rich Freeman
2014-08-30 12:55 ` Lars Wendler
2014-08-30 13:45 ` Rich Freeman
2014-09-03 18:11 ` William Hubbs [this message]
2014-09-03 18:19 ` Ian Stakenvicius
2014-09-03 18:45 ` William Hubbs
2014-09-03 19:27 ` Rich Freeman
2014-09-10 3:29 ` [gentoo-dev] " Steven J. Long
2014-08-30 12:05 ` [gentoo-dev] " J. Roeleveld
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=20140903181114.GA14334@linux1 \
--to=williamh@gentoo.org \
--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