From: Jean-Christophe DUBOIS <jcd@tribudubois.net>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH v6] bcache-tools: Adding package.
Date: Sun, 07 Sep 2014 22:27:19 +0200 [thread overview]
Message-ID: <540CBFA7.3070603@tribudubois.net> (raw)
In-Reply-To: <20140907091826.GA31418@free.fr>
Le 09/07/2014 11:18 AM, Yann E. MORIN a ?crit :
> Jean-Christophe, All,
>
> On 2014-09-07 11:14 +0200, Yann E. MORIN spake thusly:
>> On 2014-09-07 09:21 +0200, Jean-Christophe DUBOIS spake thusly:
>>> Le 09/06/2014 12:42 PM, Yann E. MORIN a ?crit :
>> [--SNIP--]
>>>>> diff --git a/package/bcache-tools/bcache-tools.mk b/package/bcache-tools/bcache-tools.mk
>>>>> new file mode 100644
>>>>> index 0000000..880bf5e
>>>>> --- /dev/null
>>>>> +++ b/package/bcache-tools/bcache-tools.mk
>>>>> @@ -0,0 +1,31 @@
>>>>> +################################################################################
>>>>> +#
>>>>> +# bcache-tools
>>>>> +#
>>>>> +################################################################################
>>>>> +
>>>>> +BCACHE_TOOLS_VERSION = v1.0.7
>>>>> +BCACHE_TOOLS_SITE = $(call github,g2p,bcache-tools,$(BCACHE_TOOLS_VERSION))
>>>>> +BCACHE_TOOLS_LICENSE = GPLv2
>>>>> +BCACHE_TOOLS_LICENSE_FILES = COPYING
>>>>> +BCACHE_TOOLS_DEPENDENCIES = host-pkgconf util-linux eudev
>>>> ... so you do not need to depend on it here, just in the Config.in file.
>>> Well, I need to make sure that "udev" is build before bcache-tools because
>>> it tries to put files in the /lib/udev/ directory of the target file system
>>> ans this directory doesn't exist before the udev package is built.
>> In this case, just add:
>>
>> # bcache-tools forgets to create the required directory... :-/
>> define BCACHE_TOOLS_UDEV_DIR
>> mkdir -p $(TARGET_DIR)/lib/udev/
>> endef
>> BCACHE_TOOLS_PRE_INSTALL_TARGET_HOOKS += BCACHE_TOOLS_UDEV_DIR
>>
>> And you're done. ;-)
> Of course, since cafeine hasn't yet fully kicked-in in my body, this
> can/should be squashed in the existing PRE_INSTALL hook which creates
> the man8 directory.
OK, I'll do it this way.
Now just for my information, why is it better to force the creation of a
missing directory rather
than force as a dependency the build of the package bringing this directory?
JC
>
> Regards,
> Yann E. MORIN.
>
next prev parent reply other threads:[~2014-09-07 20:27 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-08-08 16:11 [Buildroot] [PATCH v6] bcache-tools: Adding package Jean-Christophe DUBOIS
2014-08-08 17:03 ` Jean-Christophe DUBOIS
2014-08-27 5:45 ` Jean-Christophe DUBOIS
2014-08-27 12:52 ` Matthew Weber
2014-09-06 10:42 ` Yann E. MORIN
2014-09-07 7:21 ` Jean-Christophe DUBOIS
2014-09-07 9:14 ` Yann E. MORIN
2014-09-07 9:18 ` Yann E. MORIN
2014-09-07 20:27 ` Jean-Christophe DUBOIS [this message]
2014-09-07 20:34 ` Yann E. MORIN
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=540CBFA7.3070603@tribudubois.net \
--to=jcd@tribudubois.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox