Util-Linux package development
 help / color / mirror / Atom feed
From: L A Walsh <lkml@tlinx.org>
To: Bruce Dubbs <bruce.dubbs@gmail.com>
Cc: util-linux@vger.kernel.org
Subject: Re: configure output seems confusing in util-linux-2.32
Date: Tue, 01 May 2018 20:33:50 -0700	[thread overview]
Message-ID: <5AE9319E.6050105@tlinx.org> (raw)
In-Reply-To: <0a977638-61e0-2ffc-8b3e-e4c9dcbaea2a@gmail.com>

Bruce Dubbs wrote:
> On 05/01/2018 07:39 PM, L A Walsh wrote:
>   
>> Looked at configure help, saw:
>> Optional packages:
>> ...
>>   --with-systemd          build with support for systemd
>> to me, this means systemd is optional and may be
>> included using a 'with'.
>> Conversely, one could use:
>>   --without-systemd
>>     
>
> Works for me,  but you also need to use --without-systemdsystemunitdir
>   
---
    I see.
    That's a workaround to suppress the message.  Even without
the '--without-systemdsystemunitdir', systemd appears to be
disabled.  Under the summary of options, it had:

  Bash completions:  /usr/share/bash-completion
  Systemd support:   no
  Btrfs support:     yes
  Wide-char support: yes

    It seems like it is more confusing than
an actual problem.  Though, IMO, "--without-systemd"
should disable any processing for the systemd unit dir as well,
no?  And going with standard meanings, if the switch to toggle
default behavior is the one listed in "configure --help", wouldn't
the default have been --without-systemdsystemunitdir (boy that's
a mouthful of a switch name)?

    AFAIK, this issue is more along the lines of dotting an 'i'
or crossing a 't', but it's still a bit odd...

-l




  reply	other threads:[~2018-05-02  3:33 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-05-02  0:39 configure output seems confusing in util-linux-2.32 L A Walsh
2018-05-02  2:53 ` Bruce Dubbs
2018-05-02  3:33   ` L A Walsh [this message]
2018-05-03  8:27     ` Karel Zak

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=5AE9319E.6050105@tlinx.org \
    --to=lkml@tlinx.org \
    --cc=bruce.dubbs@gmail.com \
    --cc=util-linux@vger.kernel.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