Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Karoly Kasza <kaszak@gmail.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH] package/openvmtools: move files up from unnecessary subdirectory
Date: Wed, 17 Jun 2015 09:33:36 +0200	[thread overview]
Message-ID: <1434526416-62466-1-git-send-email-kaszak@gmail.com> (raw)

The Open-vm-tools package is now distributed from GitHub and a new
subdirectory was introduced, which breaks the Buildroot process.

This patch moves everything up from the new subdirectory after
extraction, making Buildroot once again able to run.

Fixes:

http://autobuild.buildroot.net/results/bfd10c8d454a2686ebb1c4afdb49c55e39a9dd67/

Signed-off-by: Karoly Kasza <kaszak@gmail.com>
---
 package/openvmtools/openvmtools.mk | 7 +++++++
 1 file changed, 7 insertions(+)

diff --git a/package/openvmtools/openvmtools.mk b/package/openvmtools/openvmtools.mk
index 822bbf1..414a42a 100644
--- a/package/openvmtools/openvmtools.mk
+++ b/package/openvmtools/openvmtools.mk
@@ -44,6 +44,13 @@ else
 OPENVMTOOLS_CONF_OPTS += --without-pam
 endif
 
+# Move everything up from the unnecessary subdirectory
+define OPENVMTOOLS_POST_EXTRACT_MOVE_SUBDIR
+	mv $(@D)/open-vm-tools/* $(@D)
+endef
+
+OPENVMTOOLS_POST_EXTRACT_HOOKS += OPENVMTOOLS_POST_EXTRACT_MOVE_SUBDIR
+
 # symlink needed by lib/system/systemLinux.c (or will cry in /var/log/messages)
 # defined in lib/misc/hostinfoPosix.c
 # /sbin/shutdown needed for Guest OS restart/shutdown from hypervisor
-- 
2.1.4

             reply	other threads:[~2015-06-17  7:33 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-06-17  7:33 Karoly Kasza [this message]
2015-06-17  7:44 ` [Buildroot] [PATCH] package/openvmtools: move files up from unnecessary subdirectory Thomas Petazzoni
2015-06-17  7:47   ` Károly Kasza
2015-06-17  7:51     ` Károly Kasza
2015-06-17  8:00       ` Thomas Petazzoni

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=1434526416-62466-1-git-send-email-kaszak@gmail.com \
    --to=kaszak@gmail.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