From: "W. Trevor King" <wking@tremily.us>
To: gentoo-catalyst@lists.gentoo.org
Cc: Brian Dolbec <dolsen@gentoo.org>
Subject: Re: [gentoo-catalyst] [PATCH 3/3] Fix a relative path bug
Date: Tue, 17 Dec 2013 19:48:02 -0800 [thread overview]
Message-ID: <20131218034802.GH25409@odin.tremily.us> (raw)
In-Reply-To: <1387329131-25890-4-git-send-email-dolsen@gentoo.org>
[-- Attachment #1: Type: text/plain, Size: 995 bytes --]
What's the bug? More details in the commit message would be good.
On Tue, Dec 17, 2013 at 05:12:11PM -0800, Brian Dolbec wrote:
> - local destdir=".${subdir}/tmp"
> + local destdir="${subdir}/tmp"
> …
> copy_to_chroot ${1} ${destdir}
> @@ -33,7 +33,7 @@ exec_in_chroot(){
> chmod +x ${chroot_path}/${destdir}/${file_name}
If we're requiring ${subdir} (and thus ${destdit}) to be an absolute
chroot path, you may want to fix this too.
> echo "Running ${file_name} in chroot ${chroot_path}"
> - ${clst_CHROOT} ${chroot_path} ${destdir}/${file_name} || exit 1
> + ${clst_CHROOT} ${chroot_path} .${destdir}/${file_name} || exit 1
Do we need the leading dot here? Can we store:
file_path="${chroot_path}/${destdir}/${file_name}"
and use that for both the chmod and clst_CHROOT calls?
Cheers,
Trevor
--
This email may be signed or encrypted with GnuPG (http://www.gnupg.org).
For more information, see http://en.wikipedia.org/wiki/Pretty_Good_Privacy
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 836 bytes --]
prev parent reply other threads:[~2013-12-18 3:48 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-12-18 1:12 [gentoo-catalyst] Path addition fixes to prevent multiple slashes in paths Brian Dolbec
2013-12-18 1:12 ` [gentoo-catalyst] [PATCH 1/3] Remove some troublesome trailing slashes from paths Brian Dolbec
2013-12-18 3:41 ` W. Trevor King
2013-12-18 5:40 ` Brian Dolbec
2013-12-18 1:12 ` [gentoo-catalyst] [PATCH 2/3] Remove an extra slash in the path Brian Dolbec
2013-12-18 3:42 ` W. Trevor King
2013-12-18 1:12 ` [gentoo-catalyst] [PATCH 3/3] Fix a relative path bug Brian Dolbec
2013-12-18 3:48 ` W. Trevor King [this message]
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=20131218034802.GH25409@odin.tremily.us \
--to=wking@tremily.us \
--cc=dolsen@gentoo.org \
--cc=gentoo-catalyst@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