Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH 1/2] util-linux: add menu items for login utilities
Date: Thu, 24 Aug 2017 23:24:03 +0200	[thread overview]
Message-ID: <20170824232403.1a196068@windsurf> (raw)
In-Reply-To: <20170824035838.14466-1-casantos@datacom.ind.br>

Hello,

On Thu, 24 Aug 2017 00:58:37 -0300, Carlos Santos wrote:

> +config BR2_PACKAGE_UTIL_LINUX_LOGIN_UTILS
> +	bool "login utilities option removed"

	bool "util-linux login utilities option removed"

> +	depends on BR2_USE_MMU # fork() (login, runuser, su, sulogin)
> +	depends on (BR2_ENABLE_LOCALE && BR2_USE_WCHAR) # linux-pam
> +	depends on !BR2_STATIC_LIBS
> +	depends on !BR2_TOOLCHAIN_USES_MUSL # linux-pam

All those "depends on" can be dropped.

> +	select BR2_LEGACY
> +	select BR2_PACKAGE_UTIL_LINUX_LAST
> +	select BR2_PACKAGE_UTIL_LINUX_LOGIN
> +	select BR2_PACKAGE_UTIL_LINUX_RUNUSER
> +	select BR2_PACKAGE_UTIL_LINUX_SU
> +	select BR2_PACKAGE_UTIL_LINUX_SULOGIN
> +	help
> +	  Login utilities (last, login, runuser, su, sulogin) now have
> +	  their own selecion items in the configuration menu.

selecion -> selection

Perhaps you can say "in the util-linux package configuration options" or
something like this.

> -comment "login utilities needs a uClibc or glibc toolchain w/ wchar, locale, dynamic library"
> -	depends on !(BR2_ENABLE_LOCALE && BR2_USE_WCHAR) \
> -		|| BR2_STATIC_LIBS || BR2_TOOLCHAIN_USES_MUSL
> -
>  config BR2_PACKAGE_UTIL_LINUX_LOGGER
>  	bool "logger"
>  	help
>  	  Enter messages into the system log
>  
> +config BR2_PACKAGE_UTIL_LINUX_LOGIN
> +	bool "login"
> +	depends on (BR2_ENABLE_LOCALE && BR2_USE_WCHAR) # linux-pam

Should be split on two lines, one per depends on. I know it wasn't like
that before, but let's take this opportunity to fix it.

> +	depends on !BR2_TOOLCHAIN_USES_MUSL # linux-pam
> +	depends on BR2_USE_MMU # fork(), linux-pam
> +	select BR2_PACKAGE_LINUX_PAM
> +	help
> +	  Begin a session on the system

Missing Config.in comment.

Otherwise, looks OK to me. So, by the time you send the next iteration,
if nobody else complains, I'll apply.

Best regards,

Thomas
-- 
Thomas Petazzoni, CTO, Free Electrons
Embedded Linux and Kernel engineering
http://free-electrons.com

  parent reply	other threads:[~2017-08-24 21:24 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-08-19 23:55 [Buildroot] [PATCH] util-linux: add menu items for login utilities Carlos Santos
2017-08-23 13:42 ` Thomas Petazzoni
2017-08-23 16:51   ` Carlos Santos
2017-08-24  3:58   ` [Buildroot] [PATCH 1/2] " Carlos Santos
2017-08-24  3:58     ` [Buildroot] [PATCH 2/2] util-linux: use a patch from upstream to fix ncursesw support Carlos Santos
2017-08-24 21:21       ` Thomas Petazzoni
2017-08-24 21:24     ` Thomas Petazzoni [this message]
2017-08-25  3:19       ` [Buildroot] [PATCH v3] util-linux: add menu items for login utilities Carlos Santos
2017-08-25 20:51         ` Arnout Vandecappelle
2017-08-25 21:26           ` [Buildroot] [PATCH v4] " Carlos Santos
2017-09-02  0:41             ` [Buildroot] [PATCH v5] " Carlos Santos
2017-09-02 20:49               ` Thomas Petazzoni

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=20170824232403.1a196068@windsurf \
    --to=thomas.petazzoni@free-electrons.com \
    --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