From: Ryan Barnett <ryan.barnett@rockwellcollins.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH v8] package/sysdig: New package
Date: Wed, 25 Mar 2015 16:20:14 -0500 [thread overview]
Message-ID: <CAMQcK5+8PT1KpzDG-FRXLd2G2+rOGtMN3tmPWDyadLx+14YJTg@mail.gmail.com> (raw)
In-Reply-To: <20150325194753.3cf82e93@free-electrons.com>
Thomas,
On Wed, Mar 25, 2015 at 1:47 PM, Thomas Petazzoni
<thomas.petazzoni@free-electrons.com> wrote:
>
> Well, it depends. If those dependencies are indeed mandatory (i.e
> sysdig always needs LuaJIT, be it a bundled version or a
> system-provided version), I believe we generally prefer to always use
> the system-generated version. Using bundling version is not really nice
> to make sure that the latest versions of LuaJit/zlib/jsoncpp are used.
>
> So, in general, I think we prefer to use system-provided versions,
> unless using the bundled version is absolutely necessary (tight version
> dependency, specific hacks done, etc.).
Thank you for the clarification! So he is correct in forcing
luajit/zlib/jsoncpp to be build in your target.
Thanks,
-Ryan
--
Ryan Barnett / Sr Software Engineer
Airborne Information Systems / Security Systems and Software
MS 131-100, C Ave NE, Cedar Rapids, IA, 52498, USA
ryan.barnett at rockwellcollins.com
www.rockwellcollins.com
next prev parent reply other threads:[~2015-03-25 21:20 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-03-25 10:53 [Buildroot] [PATCH v8] package/sysdig: New package Angelo Compagnucci
2015-03-25 10:56 ` Yegor Yefremov
2015-03-25 18:05 ` Ryan Barnett
2015-03-25 18:29 ` Ryan Barnett
2015-03-25 18:47 ` Thomas Petazzoni
2015-03-25 21:20 ` Ryan Barnett [this message]
2015-03-25 21:50 ` Angelo Compagnucci
2015-03-25 21:56 ` Ryan Barnett
2015-03-26 15:17 ` Angelo Compagnucci
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=CAMQcK5+8PT1KpzDG-FRXLd2G2+rOGtMN3tmPWDyadLx+14YJTg@mail.gmail.com \
--to=ryan.barnett@rockwellcollins.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 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.