From: "Jérôme Pouiller" <jezz@sysmic.org>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH 3/4] libfslparser: add install hooks to fix libraries path
Date: Mon, 09 Nov 2015 09:43:56 +0100 [thread overview]
Message-ID: <3216905.pxiEsz4o6j@sagittea> (raw)
In-Reply-To: <CAAMH-yvbFV0i_RfRu91apJRbz4TQ3DYCr8bB4ERKQ4afPtZ5zA@mail.gmail.com>
On Sunday 08 November 2015 17:08:43 Gary Bisson wrote:
> Hi J?r?me,
>
> On Fri, Oct 30, 2015 at 11:43 AM, J?r?me Pouiller <jezz@sysmic.org>
wrote:
> > On Friday 30 October 2015 11:36:21 Gary Bisson wrote:
[...]
> >> Although it might have been more consistent to have the staging
> >> hook
> >> in both, I chose to reduce the patch as much as possible. Plus I'm
> >> not sure people will like my symlink approach in the staging
> >> directory.>
> > IMHO, target/ should be a subset of staging/ (even if today, this is
> > far from the case). So, I would prefer to also create symlinks in
> > staging/.
> So I'm ok with adding the symlinks to the fslparser staging as well.
> But if we'd really like to have target as a subset of staging,
> shouldn't we use symlinks for the target too?
Sure, I am in favor to use symlinks for target/ also.
BR,
--
J?r?me Pouiller, Sysmic
Embedded Linux specialist
http://www.sysmic.fr
next prev parent reply other threads:[~2015-11-09 8:43 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-10-29 20:06 [Buildroot] [PATCH 0/4] libfsl*: fix install path + update conf opts Gary Bisson
2015-10-29 20:06 ` [Buildroot] [PATCH 1/4] libfslcodec: add install hooks to fix libraries path Gary Bisson
2015-10-29 20:06 ` [Buildroot] [PATCH 2/4] libfslcodec: add missing configure options Gary Bisson
2015-10-29 20:06 ` [Buildroot] [PATCH 3/4] libfslparser: add install hooks to fix libraries path Gary Bisson
2015-10-30 10:27 ` Jérôme Pouiller
2015-10-30 10:36 ` Gary Bisson
2015-10-30 10:43 ` Jérôme Pouiller
2015-11-08 16:08 ` Gary Bisson
2015-11-09 8:43 ` Jérôme Pouiller [this message]
2015-10-29 20:06 ` [Buildroot] [PATCH 4/4] libfslparser: add missing configure options Gary Bisson
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=3216905.pxiEsz4o6j@sagittea \
--to=jezz@sysmic.org \
--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