From: Jesse Zhang <sen.zhang@windriver.com>
To: Richard Purdie <richard.purdie@linuxfoundation.org>,
<nitin.a.kamble@intel.com>
Cc: openembedded-core@lists.openembedded.org
Subject: Re: [PATCH] coreutils: remove dependency on coreutils-native
Date: Thu, 17 Jan 2013 10:09:26 +0800 [thread overview]
Message-ID: <50F75D56.3050005@windriver.com> (raw)
In-Reply-To: <1358337581.8129.2.camel@ted>
On 01/16/2013 07:59 PM, Richard Purdie wrote:
> Two questions:
>
> 1) Why do we have this dependency here at all? Are we sure we don't need
> it for some reasons?
It was introduced in this commit, Cc'ing Nitin.
commit 543577c25b5a4e89a3ab15ee28e754b71c2a43d5
Author: Nitin A Kamble <nitin.a.kamble@intel.com>
Date: Thu Mar 17 10:25:04 2011 -0700
coreutils-6.9: fix man page building for the gplv2 recipe
But the reason behind the dependency is not entirely clear. And we've
never seen such issue with the GPLv3 recipe. (And the GPLv2 recipe with
my fix has been building well here for some time).
> 2) Isn't the build of coreutils-native still broken? We should probably
> hack it so it installs into some path prefix like
> {python/perl/gzip/tar}-native or doesn't install the utils at all.
Yeah, the build would still be broken.
The main contents of coreutils are the several dozen commands. I'm not
sure how it can be useful if we install them into a not-in-$PATH dir.
Any suggestions? I'm willing to work out a fix.
jesse
next prev parent reply other threads:[~2013-01-17 2:24 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-01-15 7:16 [PATCH] coreutils: remove dependency on coreutils-native Jesse Zhang
2013-01-15 7:16 ` Jesse Zhang
2013-01-16 11:59 ` Richard Purdie
2013-01-17 2:09 ` Jesse Zhang [this message]
2013-01-17 5:37 ` Kamble, Nitin A
2013-01-17 6:15 ` Jesse Zhang
2013-01-17 20:22 ` Richard Purdie
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=50F75D56.3050005@windriver.com \
--to=sen.zhang@windriver.com \
--cc=nitin.a.kamble@intel.com \
--cc=openembedded-core@lists.openembedded.org \
--cc=richard.purdie@linuxfoundation.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