public inbox for gentoo-dev@lists.gentoo.org
 help / color / mirror / Atom feed
From: Thomas Deutschmann <whissi@gentoo.org>
To: gentoo-dev@lists.gentoo.org
Subject: Re: [gentoo-dev] newsitem: openrc runscript transition (draft 3)
Date: Thu, 25 Aug 2016 00:51:42 +0200	[thread overview]
Message-ID: <8eaecf9c-3ff3-109f-bcba-8caacaa58d53@gentoo.org> (raw)
In-Reply-To: <20160824215946.GA26740@whubbs1.gaikai.biz>


[-- Attachment #1.1: Type: text/plain, Size: 2861 bytes --]

On 2016-08-24 23:59, William Hubbs wrote:
> Since OpenRC is used outside of Gentoo, a warning like this would have
> to be:
> 
> * /etc/init.d/test uses runscript and must be converted to openrc-run
> * For more details see the OpenRC NEWS file
> 
> because we don't know where or if the file will be installed by
> downstreams.

Yes, this will be the message in OpenRC's SRC. However you could patch
that message for Gentoo in the ebuild.


>> In "/usr/share/doc/openrc-*/openrc-migration*" we describe _why_ this
>> was changed and tell them that all files in FILESDIR were already
>> migrated so chances are high that
>>
>>   # emerge --oneshot -av $(grep -l '/sbin/runscript' /etc/init.d/*)
>>
>> will replace most runscripts with migrated scripts.
>>
>> If the user has already done that he/she should check which packages
>> owns the runscript (qfile /etc/init.d/foo) and should file a bug against
>> that package.
> 
> We can't really put anything distro-specific in the news file, because we
> don't know how distros will handle it.

...now with the patched message you can promote our own file. And this
file can get installed from $FILESDIR for example.

You are using GitHub for OpenRC upstream, right? So create a guide in
project's Wiki (or add it to the docs folder in the src) which will
explain the changes. This guide can have a section to explain what to do
on Debian, one for Gentoo... but this is all upstream.

My point is, that for Gentoo downstream, you can patch/customize like we
do for all the other packages to work with Gentoo.


>> And as additional help sys-apps/openrc ebuild should start scanning for
>> "/sbin/runscript" usage in pkg_postinst and show an ewarn with text
> 
> I wouldn't say that the OpenRC ebuild should be concerned about this,
> but I believe there is a check in repoman for it.

I agree. However I see that more like a service for Gentoo users. Users
don't run repoman. And don't forget that the user could have _custom_
runscripts or additional packages from other sources which repoman will
never see... so it is nice to have a friendly reminder (the problem is,
that if an user acts _now_ and fixes all currently installed runscripts
he/she could face the problem in future again if he/she installs a new
package after that which wasn't updated yet... that's why I would add
such a scan).


...and we don't need to believe to catch all the runscripts in the world
even if openrc-1.0.0 will be released in 100y. Some user will finally
notice with the newsitem prior openrc-1.0.0 release which will tell them
that /sbin/runscript was finally removed... but there _will_ be users
after that which will get hit. And they will complain "you" broke their
system despite all the effort to prevent such situations. ;-)


-- 
Regards,
Thomas



[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 951 bytes --]

      reply	other threads:[~2016-08-24 22:52 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
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 [this message]

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=8eaecf9c-3ff3-109f-bcba-8caacaa58d53@gentoo.org \
    --to=whissi@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