From: Ralph Sennhauser <sera@gentoo.org>
To: gentoo-pms@lists.gentoo.org
Subject: Re: [gentoo-pms] Mention xargs?
Date: Sat, 18 Aug 2012 01:08:57 +0200 [thread overview]
Message-ID: <20120818010857.3a5310dc@sera-17.lan> (raw)
In-Reply-To: <20521.60179.246986.493041@a1i15.kph.uni-mainz.de>
On Tue, 14 Aug 2012 08:07:15 +0200
Ulrich Mueller <ulm@gentoo.org> wrote:
> >>>>> On Sun, 12 Aug 2012, Ralph Sennhauser wrote:
>
> >> When preparing the list of EAPI 5 features for the upcoming council
> >> meeting, I noticed that the eapi-5 branch mentions only GNU find
> >> [1] whereas the corresponding bug mentions both find and xargs [2].
> >>
> >> Shouldn't we mention xargs, too?
>
> > Usually I see xargs used as 'find <somestuff> | xargs <dosomething>'
> > which can easily be handled by find alone. So, not sure we want to
> > mandate xargs at all.
>
> Well, xargs is mandated by POSIX, so it will be present in the system
> anyway. So we'd better make sure that the implementations of find and
> xargs match.
>
> This would also agree with current practice. For example, the
> following is done in profiles/default/bsd/fbsd/profile.bashrc:
>
> type -P gfind > /dev/null && alias find=gfind
> type -P gxargs > /dev/null && alias xargs=gxargs
>
> Another small issue, the package isn't named "find" but "findutils":
> <http://git.overlays.gentoo.org/gitweb/?p=proj/pms.git;a=commit;h=6a95dae3fa6b8a6307f5d02c09dc550f1fbe97f2>
>
> Ulrich
>
I see where you are coming from, however, the first thing that comes to
mind is, there should be a paragraph in the devmanual "useless use of
xargs" as there is for cat.
Ralph
next prev parent reply other threads:[~2012-08-17 23:09 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-08-12 8:56 [gentoo-pms] Mention xargs? Ulrich Mueller
2012-08-12 10:08 ` Ralph Sennhauser
2012-08-14 6:07 ` Ulrich Mueller
2012-08-17 23:08 ` Ralph Sennhauser [this message]
2012-08-18 7:39 ` Ulrich Mueller
2012-08-16 21:50 ` [gentoo-pms] " Ulrich Mueller
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=20120818010857.3a5310dc@sera-17.lan \
--to=sera@gentoo.org \
--cc=gentoo-pms@lists.gentoo.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