From: Kent Fredric <kentnl@gentoo.org>
To: gentoo-dev@lists.gentoo.org
Subject: Re: [gentoo-dev] newsitem: openrc runscript transition (draft 3)
Date: Thu, 25 Aug 2016 03:17:06 +1200 [thread overview]
Message-ID: <20160825031706.272c2dae@katipo2.lan> (raw)
In-Reply-To: <20160824145921.GA7100@waltdnes.org>
[-- Attachment #1: Type: text/plain, Size: 1140 bytes --]
On Wed, 24 Aug 2016 10:59:21 -0400
waltdnes@waltdnes.org wrote:
> These things get left in forever. I once filed a bug report
> https://bugs.gentoo.org/show_bug.cgi?id=569056 because the warning that
> English word lists in vim had been removed was still present *TWO YEARS*
> after the fact.
>
> How flexible is the ewarn option? Can printing the warning be made
> conditional? I suggest warning only if there are any hits on...
>
> grep -l '^#!/sbin/runscript' /etc/init.d/*
>
> Note the single-quote around the expression. Otherwise "#" can be a
> special character for grep. Furthermore, "grep -l" output can be used
> to tell the enduser which specific scripts are non-compliant.
There's a few other options we can use here as well ...
1. GLEP 65, but I'm still not entirely sure how all this works.
https://wiki.gentoo.org/wiki/GLEP:65
2. pkg_postinst
3. pkg_info
https://devmanual.gentoo.org/ebuild-writing/functions/pkg_info/index.html
With #3 that means
emerge --info sys-devel/openrc
Could fire up a quick grep and tell users which specific things need fixing still.
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 819 bytes --]
next prev parent reply other threads:[~2016-08-24 15:17 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-08-22 22:57 [gentoo-dev] newsitem: openrc runscript transition (draft 3) William Hubbs
2016-08-24 7:32 ` Kent Fredric
2016-08-24 12:08 ` Jason Zaman
2016-08-24 13:58 ` [gentoo-dev] " Duncan
2016-08-24 14:59 ` [gentoo-dev] " waltdnes
2016-08-24 15:17 ` Kent Fredric [this message]
2016-08-24 17:07 ` William Hubbs
2016-08-24 17:41 ` Thomas Deutschmann
2016-08-24 21:59 ` William Hubbs
2016-08-24 22:51 ` Thomas Deutschmann
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=20160825031706.272c2dae@katipo2.lan \
--to=kentnl@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