From: "Luca Bocassi" <luca.boccassi@gmail.com>
To: Khem Raj <raj.khem@gmail.com>,
Richard Purdie <richard.purdie@linuxfoundation.org>
Cc: Patches and discussions about the oe-core layer
<openembedded-core@lists.openembedded.org>
Subject: Re: [OE-core] [PATCH] Add new recipe for squashfs-tools-ng
Date: Thu, 22 Oct 2020 10:13:01 +0100 [thread overview]
Message-ID: <fe0fdbecda63255e6b15ff90df677989b5f4a579.camel@gmail.com> (raw)
In-Reply-To: <CAMKF1sqeeYnhu_677KdPLeSa_D3mMJO6oPADEpxS0hVsaLH_Nw@mail.gmail.com>
On Wed, 2020-10-21 at 19:21 -0700, Khem Raj wrote:
> On Wed, Oct 21, 2020 at 12:02 PM Richard Purdie
> <richard.purdie@linuxfoundation.org> wrote:
> > On Wed, 2020-10-21 at 16:58 +0100, Luca Bocassi wrote:
> > > From: Luca Boccassi <luca.boccassi@microsoft.com>
> > >
> > > The main difference with squashfs-tools is the availability
> > > of a shared library and a programmatic interface, rather
> > > than just command-line tools.
> > >
> > > Signed-off-by: Luca Boccassi <luca.boccassi@microsoft.com>
> > > ---
> > > .../squashfs-tools-ng_git.bb | 37
> > > +++++++++++++++++++
> > > 1 file changed, 37 insertions(+)
> > > create mode 100644 meta/recipes-devtools/squashfs-tools-ng/squashfs-
> > > tools-ng_git.bb
> >
> > Should we be switching over to squashfs-tools-ng and removing squashfs-
> > tools? I'm not sure we want to support both versions?
>
> I am not sure if we want to switch to ng yet as on option its good to
> have. Perhaps in meta-oe or some other place.
Yeah the command line interface is not a one-to-one mapping, so
probably best to keep both around.
--
Kind regards,
Luca Boccassi
next prev parent reply other threads:[~2020-10-22 9:13 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-10-21 15:58 [PATCH] Add new recipe for squashfs-tools-ng Luca Bocassi
2020-10-21 19:02 ` [OE-core] " Richard Purdie
2020-10-22 2:21 ` Khem Raj
2020-10-22 9:13 ` Luca Bocassi [this message]
2020-10-21 19:08 ` Konrad Weihmann
2020-10-22 9:21 ` Luca Bocassi
2020-10-22 9:20 ` [PATCH v2] " Luca Bocassi
2020-10-22 11:10 ` [OE-core] " Peter Kjellerstedt
2020-10-22 11:30 ` Luca Bocassi
2020-10-22 11:30 ` [PATCH v3] " Luca Bocassi
2020-10-22 19:10 ` [OE-core] " Khem Raj
2020-10-23 8:57 ` Luca Bocassi
2020-10-24 12:58 ` Richard Purdie
2020-10-26 10:05 ` Luca Bocassi
2020-10-26 10:05 ` [PATCH v4] " Luca Bocassi
2020-10-26 10:29 ` Richard Purdie
2020-10-26 13:09 ` Luca Bocassi
2020-10-27 10:31 ` Luca Bocassi
2020-10-27 10:37 ` Richard Purdie
2020-10-27 10:59 ` Luca Bocassi
2020-10-27 11:19 ` [OE-core] " Ross Burton
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=fe0fdbecda63255e6b15ff90df677989b5f4a579.camel@gmail.com \
--to=luca.boccassi@gmail.com \
--cc=openembedded-core@lists.openembedded.org \
--cc=raj.khem@gmail.com \
--cc=richard.purdie@linuxfoundation.org \
/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.