From: bugzilla at busybox.net <bugzilla@busybox.net>
To: buildroot@busybox.net
Subject: [Buildroot] [Bug 4339] New: Allow override of DL_DIR in extract step
Date: Thu, 20 Oct 2011 02:53:20 +0000 (UTC) [thread overview]
Message-ID: <bug-4339-163@https.bugs.busybox.net/> (raw)
https://bugs.busybox.net/show_bug.cgi?id=4339
Summary: Allow override of DL_DIR in extract step
Product: buildroot
Version: unspecified
Platform: PC
OS/Version: Linux
Status: NEW
Severity: enhancement
Priority: P5
Component: Other
AssignedTo: unassigned at buildroot.uclibc.org
ReportedBy: d_mo1234 at yahoo.com
CC: buildroot at uclibc.org
Estimated Hours: 0.0
Created attachment 3649
--> https://bugs.busybox.net/attachment.cgi?id=3649
patch file
I am updating from an older version of buildroot to the latest. I find it
useful to override the value of DL_DIR for certain packages, to sequester the
downloaded package in a different area than all the other third party packages.
However, I found that the [relatively] recent introduction of
"$(2)_EXTRACT_CMDS" in package/Makefile.package.in broke this, because the
definition is using $(DL_DIR) instead of $$(DL_DIR) like in other templates in
the file. So I would like to add the extra $. Don't think that should be too
controversial.
Patch file is attached.
--
Configure bugmail: https://bugs.busybox.net/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are on the CC list for the bug.
next reply other threads:[~2011-10-20 2:53 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-10-20 2:53 bugzilla at busybox.net [this message]
2014-02-08 20:56 ` [Buildroot] [Bug 4339] Allow override of DL_DIR in extract step bugzilla at busybox.net
2014-02-08 22:04 ` bugzilla at busybox.net
2014-02-10 18:03 ` bugzilla at busybox.net
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=bug-4339-163@https.bugs.busybox.net/ \
--to=bugzilla@busybox.net \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.