public inbox for gentoo-dev@lists.gentoo.org
 help / color / mirror / Atom feed
From: Ulrich Mueller <ulm@gentoo.org>
To: Sergei Trofimovich <slyfox@gentoo.org>
Cc: gentoo-dev@lists.gentoo.org
Subject: Re: [gentoo-dev] [PATCH v3] mount-boot.eclass: Check if /boot is sane, but don't try to mount it.
Date: Sat, 07 Dec 2019 06:44:21 +0100	[thread overview]
Message-ID: <w6glfro4rm2.fsf@kph.uni-mainz.de> (raw)
In-Reply-To: <20191206235333.3addea86@sf> (Sergei Trofimovich's message of "Fri, 6 Dec 2019 23:53:33 +0000")

[-- Attachment #1: Type: text/plain, Size: 956 bytes --]

>>>>> On Sat, 07 Dec 2019, Sergei Trofimovich wrote:

>>  	# The user wants us to leave things be.
>> -	if [[ -n ${DONT_MOUNT_BOOT} ]] ; then
>> +	if [[ -n ${I_KNOW_WHAT_I_AM_DOING} ]] ; then
>>  		return 0
>>  	fi

> The rest of patch looks ok but I find I_KNOW_WHAT_I_AM_DOING
> proliferation worrying. Having enough eclasses guard things on it I
> don't really know what I am doing :)

> For example developer profile sets it on by default and disables perl
> error checks. I don't think it's intentional.

Oh, I forgot that it is set globally in the developer profile (and I
think that's a stupid idea). Indeed we should use a different variable
then.

> I suggest giving this variable a unique specific name.

Would it be acceptable to leave DONT_MOUNT_BOOT in place? It would have
the advantage that users won't have to update their config.

> And phase out ${I_KNOW_WHAT_I_AM_DOING} uses from tree completely.

That's a separate discussion.

Ulrich

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 487 bytes --]

  reply	other threads:[~2019-12-07  5:44 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-12-06 15:35 [gentoo-dev] [PATCH v3] mount-boot.eclass: Check if /boot is sane, but don't try to mount it Ulrich Müller
2019-12-06 23:53 ` Sergei Trofimovich
2019-12-07  5:44   ` Ulrich Mueller [this message]
2019-12-07  9:00     ` Sergei Trofimovich

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=w6glfro4rm2.fsf@kph.uni-mainz.de \
    --to=ulm@gentoo.org \
    --cc=gentoo-dev@lists.gentoo.org \
    --cc=slyfox@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