From: Yann E. MORIN <yann.morin.1998@free.fr>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH v6] bcache-tools: Adding package.
Date: Sun, 7 Sep 2014 22:34:51 +0200 [thread overview]
Message-ID: <20140907203451.GI31418@free.fr> (raw)
In-Reply-To: <540CBFA7.3070603@tribudubois.net>
Jean-Christophe, All,
On 2014-09-07 22:27 +0200, Jean-Christophe DUBOIS spake thusly:
> Le 09/07/2014 11:18 AM, Yann E. MORIN a ?crit :
> >On 2014-09-07 11:14 +0200, Yann E. MORIN spake thusly:
[--SNIP--]
> >>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.
OK, thanks!
> 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?
Well, the udev package is not required to build bcache-tools. It;s just
bcache-tools' Makefile that is deficient, and forgets to create the
directory to start with.
Also, it is often the case that a decvelopper needs to build just one
package to test a build failure or a version bump. The more dependencies
there are to a package, the longer the build will be, the more
frustrating it becomes to the developper, since udev is not really a
build dependency.
And, since you anyway already have a hook to create one directory, why
not use it to create the other one?
Thanks for your efforts with this patch! :-)
Regards,
Yann E. MORIN.
--
.-----------------.--------------------.------------------.--------------------.
| Yann E. MORIN | Real-Time Embedded | /"\ ASCII RIBBON | Erics' conspiracy: |
| +33 662 376 056 | Software Designer | \ / CAMPAIGN | ___ |
| +33 223 225 172 `------------.-------: X AGAINST | \e/ There is no |
| http://ymorin.is-a-geek.org/ | _/*\_ | / \ HTML MAIL | v conspiracy. |
'------------------------------^-------^------------------^--------------------'
prev parent reply other threads:[~2014-09-07 20:34 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
2014-09-07 20:34 ` Yann E. MORIN [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=20140907203451.GI31418@free.fr \
--to=yann.morin.1998@free.fr \
--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