From: "Stefan Fröberg" <stefan.froberg@petroprogram.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH] proxychains-ng: copy proxychains.conf to target dir
Date: Wed, 16 Jan 2013 13:45:53 +0200 [thread overview]
Message-ID: <50F692F1.4090800@petroprogram.com> (raw)
In-Reply-To: <87r4llmyj4.fsf@dell.be.48ers.dk>
16.1.2013 8:29, Peter Korsgaard kirjoitti:
>>>>>> "Stefan" == Stefan Fr?berg <stefan.froberg@petroprogram.com> writes:
> Stefan> proxychains installation does not copy proxychains.conf to
> Stefan> $(TARGET_DIR)/etc anymore so we have to do it manually now.
>
> Stefan> Signed-off-by: Stefan Fr?berg <stefan.froberg@petroprogram.com>
> Stefan> ---
> Stefan> package/proxychains-ng/proxychains-ng.mk | 6 ++++++
> Stefan> 1 files changed, 6 insertions(+), 0 deletions(-)
>
> Stefan> diff --git a/package/proxychains-ng/proxychains-ng.mk b/package/proxychains-ng/proxychains-ng.mk
> Stefan> index 9cf24bf..70d35b6 100644
> Stefan> --- a/package/proxychains-ng/proxychains-ng.mk
> Stefan> +++ b/package/proxychains-ng/proxychains-ng.mk
> Stefan> @@ -7,4 +7,10 @@ PROXYCHAINS_NG_VERSION = 4.4
> Stefan> PROXYCHAINS_NG_SOURCE = proxychains-$(PROXYCHAINS_NG_VERSION).tar.bz2
> Stefan> PROXYCHAINS_NG_SITE = http://downloads.sourceforge.net/project/proxychains-ng
>
> Stefan> +define PROXYCHAINS_NG_POST_INSTALL_TARGET
> Stefan> + $(INSTALL) -m 755 $(@D)/src/proxychains.conf $(TARGET_DIR)/etc
>
> Does the configuration file really need to be executable?
Uuups! sorry
> /etc is almost guaranteed to exist, but for consistency please use
> install -D . $(TARGET_DIR)/etc/proxychains.conf
>
Okay
Fixing and resubmitting
Stefan
prev parent reply other threads:[~2013-01-16 11:45 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-01-16 4:10 [Buildroot] [PATCH] proxychains-ng: copy proxychains.conf to target dir Stefan Fröberg
2013-01-16 6:29 ` Peter Korsgaard
2013-01-16 11:45 ` Stefan Fröberg [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=50F692F1.4090800@petroprogram.com \
--to=stefan.froberg@petroprogram.com \
--cc=buildroot@busybox.net \
/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