From: Ruediger Meier <sweet_f_a@gmx.de>
To: Karel Zak <kzak@redhat.com>
Cc: util-linux@vger.kernel.org
Subject: Re: [PATCH 2/2] build-sys: install missing bash completions
Date: Thu, 17 Mar 2016 17:52:27 +0100 [thread overview]
Message-ID: <201603171752.27998.sweet_f_a@gmx.de> (raw)
In-Reply-To: <20160317131320.tj343znddbo6vqex@ws.net.home>
On Thursday 17 March 2016, Karel Zak wrote:
> On Thu, Mar 17, 2016 at 11:04:06AM +0100, Ruediger Meier wrote:
> > We haven't installed these files since three years. Hopefully
> > they will work.
>
> I have added tools/checkcompletion.sh (sorry about my shell
> programming skills, it requires bash:-), so now:
>
> $ make checkcompletion
> Missing completion scripts:
> agetty
> findfs
> kill
> line
> login
> runuser
> sulogin
> switch_root
> vipw
> > +if BUILD_MOUNT
> > +dist_bashcompletion_DATA += bash-completion/mount
> > +dist_bashcompletion_DATA += bash-completion/umount
> > +endif
>
> ... and checkcompletion does not check for incomplete Makefiles of
> course, but better than nothing.
Maybe checkcompletion.sh would be more simple and safe if we do
"make install DESTDIR=/tmp/dest" and compare installed *bin/ binaries.
with installed completions (and BTW manpages!). It would also discover
Makefile bugs. I'm sure that such distcheck-hook scripts should
already exist. Like rpmlint does such checks for the distro packages
and prints warnings plus counts negative scores:
RPMLINT report:
===============
[...]
util-linux.x86_64: W: no-manual-page-for-binary flushb
util-linux.x86_64: W: no-manual-page-for-binary chrp-addnote
Each executable in standard binary directories should have a man page.
[...]
But actually the most simple way to find non-distributed
files in _general_ is IMO this:
$ make distdir
$ find util-linux-2.28.rc1-65-5ae7a/ -type f -printf "%P\n" | sort > files-dist
$ git ls-files | sort > files-git
$ diff files-git files-dist | grep "^<"
These are so few (or generic) currently that we could maintain a
whitelist "non-distributed-files". And add such a check to the
distcheck somehow.
cu,
Rudi
next prev parent reply other threads:[~2016-03-17 16:52 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-03-17 10:04 [PATCH 1/2] build-sys: no need to un-ignore tracked files Ruediger Meier
2016-03-17 10:04 ` [PATCH 2/2] build-sys: install missing bash completions Ruediger Meier
2016-03-17 11:29 ` Karel Zak
2016-03-17 13:13 ` Karel Zak
2016-03-17 13:22 ` Ruediger Meier
2016-03-17 13:36 ` Karel Zak
2016-03-17 16:52 ` Ruediger Meier [this message]
2016-03-17 18:24 ` Karel Zak
2016-03-17 22:41 ` Ruediger Meier
2016-03-17 11:27 ` [PATCH 1/2] build-sys: no need to un-ignore tracked files 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=201603171752.27998.sweet_f_a@gmx.de \
--to=sweet_f_a@gmx.de \
--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