public inbox for gentoo-dev@lists.gentoo.org
 help / color / mirror / Atom feed
From: waltdnes@waltdnes.org
To: gentoo-dev@lists.gentoo.org
Subject: Re: [gentoo-dev] newsitem: openrc runscript transition (draft 3)
Date: Wed, 24 Aug 2016 10:59:21 -0400	[thread overview]
Message-ID: <20160824145921.GA7100@waltdnes.org> (raw)
In-Reply-To: <20160824193205.0ad0f559@katipo2.lan>

On Wed, Aug 24, 2016 at 07:32:05PM +1200, Kent Fredric wrote
> On Mon, 22 Aug 2016 17:57:43 -0500
> William Hubbs <williamh@gentoo.org> wrote:
> 
> > I thought about dropping the version number from the
> > display-if-installed line, but that doesn't make sense because it means
> > that everyone, including all new installs of OpenRC after this version,
> > would have to read the newsitem.
> > 
> > William
> > 
> 
> That concern is in the wrong priority.
> 
> "Your system might break" is more important than "ugh, annoying
> news items"
> 
> Viewing the news item once per clean install is still less of a
> "Problem" than "everyone with an old system syncs, doesn't get any
> warning, upgrades openrc to a version which breaks this, and they
> brick their boot"

  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.

-- 
Walter Dnes <waltdnes@waltdnes.org>
I don't run "desktop environments"; I run useful applications


  parent reply	other threads:[~2016-08-24 14:59 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   ` waltdnes [this message]
2016-08-24 15:17     ` [gentoo-dev] " Kent Fredric
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=20160824145921.GA7100@waltdnes.org \
    --to=waltdnes@waltdnes.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