From: Michal Marek <mmarek@suse.cz>
To: Gabriel de Perthuis <g2p.code@gmail.com>
Cc: linux-kbuild@vger.kernel.org
Subject: Re: [PATCH] deb-pkg: Don't run find across mountpoints
Date: Mon, 10 Jun 2013 15:07:56 +0200 [thread overview]
Message-ID: <51B5CFAC.6050704@suse.cz> (raw)
In-Reply-To: <51B4A9D1.7070502@gmail.com>
On 9.6.2013 18:14, Gabriel de Perthuis wrote:
> Signed-off-by: Gabriel de Perthuis <g2p.code@gmail.com>
> ---
> scripts/package/builddeb | 4 ++--
> 1 file changed, 2 insertions(+), 2 deletions(-)
>
> diff --git a/scripts/package/builddeb b/scripts/package/builddeb
> index acb8650..1435f5a 100644
> --- a/scripts/package/builddeb
> +++ b/scripts/package/builddeb
> @@ -16,11 +16,11 @@ create_package() {
> local pname="$1" pdir="$2"
>
> cp debian/copyright "$pdir/usr/share/doc/$pname/"
> cp debian/changelog "$pdir/usr/share/doc/$pname/changelog.Debian"
> gzip -9 "$pdir/usr/share/doc/$pname/changelog.Debian"
> - sh -c "cd '$pdir'; find . -type f ! -path './DEBIAN/*' -printf '%P\0' \
> + sh -c "cd '$pdir'; find . -xdev -type f ! -path './DEBIAN/*' -printf '%P\0' \
What kind of mountpoint zoo do you maintain in your build tree? :) We
run a find in make clean, make mrproper and other targets. So you might
need to fix more places. But please explain your use case.
Michal
next prev parent reply other threads:[~2013-06-10 13:07 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-06-09 16:14 [PATCH] deb-pkg: Don't run find across mountpoints Gabriel de Perthuis
2013-06-10 13:07 ` Michal Marek [this message]
2013-06-10 13:15 ` Gabriel de Perthuis
2013-06-10 13:20 ` Gabriel de Perthuis
2013-06-10 13:23 ` Michal Marek
2013-06-10 14:19 ` Gabriel de Perthuis
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=51B5CFAC.6050704@suse.cz \
--to=mmarek@suse.cz \
--cc=g2p.code@gmail.com \
--cc=linux-kbuild@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