Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Yann E. MORIN <yann.morin.1998@free.fr>
To: buildroot@busybox.net
Subject: [Buildroot] [RFC PATCH v3 1/2] makedevs: only warn when xattr support disabled
Date: Tue, 30 Jul 2019 22:57:54 +0200	[thread overview]
Message-ID: <20190730205754.GH3194@scaer> (raw)
In-Reply-To: <20190730203147.21113-1-petr.vorel@gmail.com>

Petr, All,

On 2019-07-30 22:31 +0200, Petr Vorel spake thusly:
> Previously makedevs failed when xattr configuration defined while
> disabled BR2_ROOTFS_DEVICE_TABLE_SUPPORTS_EXTENDED_ATTRIBUTES.
> Therefore check for this configuration would be required
> in each use. Therefore only print warning with number of discharged lines.
> 
> No package is using this feature so far (it's used only in tests),
> thus no need to change any package config.
> 
> Signed-off-by: Petr Vorel <petr.vorel@gmail.com>
[--SNIP--]
> @@ -641,6 +640,15 @@ int main(int argc, char **argv)
>  loop:
>  		free(line);
>  	}
> +
> +	if (xattr_warned) {
> +			bb_error_msg("%u lines with xattr configuration discharged, enable "

"discharged" is not the most appropriate term. I'd have just said
"ignored".

> +					     "BR2_ROOTFS_DEVICE_TABLE_SUPPORTS_EXTENDED_ATTRIBUTES "
> +						 "to get xattr support\n",
> +					     xattr_warned);

Yes, that's nice! :-)

> +			ret = EXIT_FAILURE;

Why do you want to exit in failure?

When makedevs exits in error, then whole fakeroot script aborts even
before attempting to generate the image.

I can see two problems with that:

  - first, when iputils is enabled, then the build will by default fail,
    as xattr support is by default disabled,

  - I can very well see a scenario where xattr, and thus capabilities,
    are not desired. For example, if I need iputils, but will only ever
    call clockdiff as root, then I don't care about its capabilities.

So, I think it is nice that we warn that xattrs are dropped, but we
should not fail the build.

Regards,
Yann E. MORIN.

> +	}
> +
>  	fclose(table);
>  
>  	return ret;
> -- 
> 2.22.0
> 

-- 
.-----------------.--------------------.------------------.--------------------.
|  Yann E. MORIN  | Real-Time Embedded | /"\ ASCII RIBBON | Erics' conspiracy: |
| +33 662 376 056 | Software  Designer | \ / CAMPAIGN     |  ___               |
| +33 561 099 427 `------------.-------:  X  AGAINST      |  \e/  There is no  |
| http://ymorin.is-a-geek.org/ | _/*\_ | / \ HTML MAIL    |   v   conspiracy.  |
'------------------------------^-------^------------------^--------------------'

  parent reply	other threads:[~2019-07-30 20:57 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-07-30 20:31 [Buildroot] [RFC PATCH v3 1/2] makedevs: only warn when xattr support disabled Petr Vorel
2019-07-30 20:31 ` [Buildroot] [RFC PATCH v3 2/2] iputils: add capability for clockdiff, ping, traceroute6 Petr Vorel
2019-07-30 20:57 ` Yann E. MORIN [this message]
2019-07-30 21:42   ` [Buildroot] [RFC PATCH v3 1/2] makedevs: only warn when xattr support disabled Petr Vorel

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=20190730205754.GH3194@scaer \
    --to=yann.morin.1998@free.fr \
    --cc=buildroot@busybox.net \
    /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