Util-Linux package development
 help / color / mirror / Atom feed
From: Ruediger Meier <sweet_f_a@gmx.de>
To: Isaac Dunham <ibid.ag@gmail.com>
Cc: Karel Zak <kzak@redhat.com>, util-linux@vger.kernel.org
Subject: Re: [PATCH 1/2] tests: test_md5 prints md5sum only
Date: Wed, 6 Apr 2016 23:11:15 +0200	[thread overview]
Message-ID: <201604062311.15801.sweet_f_a@gmx.de> (raw)
In-Reply-To: <201604061940.22739.sweet_f_a@gmx.de>

On Wednesday 06 April 2016, Ruediger Meier wrote:
> On Wednesday 06 April 2016, Isaac Dunham wrote:
> > On Wed, Apr 06, 2016 at 01:33:58PM +0100, Ruediger Meier wrote:
> > > On Wednesday 06 April 2016, Karel Zak wrote:
> > > > On Wed, Apr 06, 2016 at 12:30:17PM +0200, Ruediger Meier wrote:
> > > > > We want to to use it for other tests without depending on
> > > > > gnu md5sum and without cut or awk.
> > > >
> > > > It does not seem like anything critical, both patches applied
> > > > to the next branch (will be in v2.29). Thanks.
> > >
> > > That's ok. These patches do not fix any existing problem yet.
> > > They are just one minor step to remove coreutils dependency from
> > > out tests. We would still need to fix usage of readlink, seq and
> > > truncate.
> >
> > Is this for the sake of something where you cannot expect *any*
> > coreutils-equivalent to be installed?
> > If you can't expect that, can you expect the build scripts to work?
>
> Yes, autoconf/automake/libtool generate highly portable shell
> scripts. For example the configure script even checks whether there
> is a thread-safe "mkdir -p" available or what kind of sed is
> installed.
>
> The only problems are usually caused by hand-written scripts like
> shell snippets in Makefile.am or our test scripts ;)
>
> Our tests depend on GNU extensions for md5sum, readlink, seq,
> truncate, find,  xargs, tar, sed and the shell has to be bash. That's
> all not critical but at least nice to be fixed if it doesn't make our
> scripts too ugly.
>
> > I ask because md5sum, seq, and readlink are included in every set
> > of base utilities I'm aware of, including coreutils, busybox,
> > toybox, and even sbase (the 'suckless' base utilities).
> > That said, seq and md5sum are only specified in the LSB, and
> > readlink isn't even there.
>
> md5sum is special. It's not Posix and not available or completely
> different on non-Linux systems.

Just to clarify. I wouldn't have done this patch like this for other 
projects but here in util-linux we have our own (portable) test_md5 
already since 2008. So why not using it to avoid one more GNUism!

> About seq, readlink and truncate: our test-suite is using
> non-portable GNU extenstions. I guess it would not run with busybox.
> You can similate that even with coreutils:
>
> $ POSIXLY_CORRECT=1 make check
>
> I you feel boring you may try to fix some of the mentioned GNUisms ;)
>
> cu,
> Rudi
> --
> To unsubscribe from this list: send the line "unsubscribe util-linux"
> in the body of a message to majordomo@vger.kernel.org
> More majordomo info at  http://vger.kernel.org/majordomo-info.html

  reply	other threads:[~2016-04-06 21:11 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-04-06 10:30 [PATCH 1/2] tests: test_md5 prints md5sum only Ruediger Meier
2016-04-06 10:30 ` [PATCH 2/2] tests: don't depend on GNU md5sum Ruediger Meier
2016-04-06 12:26 ` [PATCH 1/2] tests: test_md5 prints md5sum only Karel Zak
2016-04-06 12:33   ` Ruediger Meier
2016-04-06 16:40     ` Isaac Dunham
2016-04-06 17:40       ` Ruediger Meier
2016-04-06 21:11         ` Ruediger Meier [this message]
2016-04-06 21:38         ` Isaac Dunham
2016-04-06 22:36           ` Ruediger Meier
2016-04-07  7:45             ` 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=201604062311.15801.sweet_f_a@gmx.de \
    --to=sweet_f_a@gmx.de \
    --cc=ibid.ag@gmail.com \
    --cc=kzak@redhat.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