From: Duncan <1i5t5.duncan@cox.net>
To: gentoo-dev@lists.gentoo.org
Subject: [gentoo-dev] Re: newsitem: openrc runscript transition (draft 3)
Date: Wed, 24 Aug 2016 13:58:05 +0000 (UTC) [thread overview]
Message-ID: <pan$eaf07$fb12971c$29da1675$5f80f450@cox.net> (raw)
In-Reply-To: 20160824193205.0ad0f559@katipo2.lan
Kent Fredric posted on Wed, 24 Aug 2016 19:32:05 +1200 as excerpted:
> 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"
If it was a bricking concern, yes, but this isn't about bricking (at
least not within the scope of the current news item, and I'd expect
another one before runscript is actually removed), it's about warnings
that are for the user, harmless but irritating.
So the priority could arguably be different. Note that I'm not actually
saying it is (I haven't actually decided), only that unlike the possible
bricking case, it arguably could be, because the possible bricking
argument you used for justification doesn't apply.
--
Duncan - List replies preferred. No HTML msgs.
"Every nonfree program has a lord, a master --
and if you use the program, he is your master." Richard Stallman
next prev parent reply other threads:[~2016-08-24 13:58 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 ` Duncan [this message]
2016-08-24 14:59 ` waltdnes
2016-08-24 15:17 ` 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='pan$eaf07$fb12971c$29da1675$5f80f450@cox.net' \
--to=1i5t5.duncan@cox.net \
--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