From: Karel Zak <kzak@redhat.com>
To: Sami Kerola <kerolasa@iki.fi>
Cc: util-linux@vger.kernel.org, "Pádraig Brady" <P@draigBrady.com>
Subject: Re: [PATCH 3/3] chkdupexe: reimplement command in C
Date: Mon, 2 Apr 2012 13:10:29 +0200 [thread overview]
Message-ID: <20120402111029.GA1084@x2.net.home> (raw)
In-Reply-To: <1333304372-25944-4-git-send-email-kerolasa@iki.fi>
On Sun, Apr 01, 2012 at 08:19:32PM +0200, Sami Kerola wrote:
> The new version of the command is nearly identical to old. Major
> differences are:
>
> * New output is a little rough what comes to alignment. This is
> flagged as FIXME item in source.
> * The command is much quicker than perl implementation which used
> to exec ls -ldU.
> * Size of chkdupexe binary is about five times bigger than perl
> script.
I have doubts about chkdupexe, do we really need this command?
* it provides very rarely used functionality (for example nobody
complains that the command is missing in Fedora/RHEL ;-)
* it seems that you can replace it by
ls $(echo "$PATH" | tr : ' ') | sort | uniq -d
or we can extend which(1) or so...
I see two possible ways:
1) mark chkdupexe as deprecated and remove it from distros
2) or add new command (lspath ?) and get much more information from
$PATH (like duplicates, per-directory stats, per-owner stats,
per-device stats, selinux summary, suids, etc.) and make chkdupexe as
alias to the new command (just for backward compatibility).
If 2) makes sense then it would be better to have it in coreutils ;-)
CC: Padraig
... let's flame :-)
Karel
--
Karel Zak <kzak@redhat.com>
http://karelzak.blogspot.com
next prev parent reply other threads:[~2012-04-02 11:10 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-03-20 19:27 [pull] chkdupexe, a bug, version numbers and bashisms Sami Kerola
2012-03-30 15:04 ` Karel Zak
2012-04-01 18:19 ` Sami Kerola
2012-04-01 18:19 ` [PATCH 1/3] tests: hwclock: locate ntpdate by using path Sami Kerola
2012-04-02 11:22 ` Karel Zak
2012-04-01 18:19 ` [PATCH 2/3] script: error in usage() output Sami Kerola
2012-04-02 11:27 ` Karel Zak
2012-04-01 18:19 ` [PATCH 3/3] chkdupexe: reimplement command in C Sami Kerola
2012-04-02 11:10 ` Karel Zak [this message]
2012-04-02 11:53 ` Sami Kerola
2012-04-02 12:12 ` Karel Zak
2012-04-04 10:24 ` Karel Zak
2012-04-02 12:22 ` Pádraig Brady
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=20120402111029.GA1084@x2.net.home \
--to=kzak@redhat.com \
--cc=P@draigBrady.com \
--cc=kerolasa@iki.fi \
--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