public inbox for openembedded-core@lists.openembedded.org
 help / color / mirror / Atom feed
From: "Luca Bocassi" <luca.boccassi@gmail.com>
To: Richard Purdie <richard.purdie@linuxfoundation.org>,
	 openembedded-core@lists.openembedded.org
Subject: Re: [PATCH v4] Add new recipe for squashfs-tools-ng
Date: Tue, 27 Oct 2020 10:59:54 +0000	[thread overview]
Message-ID: <ed94167201a9730b0a54504e2bf0be8fc3a19c9f.camel@gmail.com> (raw)
In-Reply-To: <4d2560d4440be40ecd73020c931d5bfd83fd9b1c.camel@linuxfoundation.org>

On Tue, 2020-10-27 at 10:37 +0000, Richard Purdie wrote:
> On Mon, 2020-10-26 at 13:09 +0000, Luca Boccassi wrote:
> > On Mon, 2020-10-26 at 10:29 +0000, Richard Purdie wrote:
> > > On Mon, 2020-10-26 at 10:05 +0000, luca.boccassi@gmail.com 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>
> > > > ---
> > > > v2: added MIT, Zlib and BSD-2-Clause to LICENSE
> > > > v3: fixed CPL-3.0+ tag, removed GPL2 from checksum (not used),
> > > > changed
> > > >     recipe to be versioned, use bb.utils.filter in PACKAGE_CONFIG
> > > > v4: disable zstd support by default, dependency not available in
> > > > oe-
> > > > core
> > > 
> > > Sorry, there is one other issue. There is no maintainers entry for
> > > this
> > > recipe (see meta/conf/distro/include/maintainers.inc) which would
> > > cause
> > > oe-selftest to fail. Can you add an maintainers entry please?
> > > 
> > > Thanks,
> > > Richard
> > 
> > Ok - who should be listed as maintainer?
> 
> The person who is going to look after this recipe in OE-Core. Each
> recipe needs to have a maintainer listed, someone who is prepared to
> get the upgrade helper emails, handle upgrades, help with security
> issues, bugs related to the recipe and so on.
> 
> If we don't have anyone willing to maintain it, I'd argue its not
> important enough to have in OE-Core...
> 
> Cheers,
> 
> Richard

Ok, I'll move to meta-openembedded then.

-- 
Kind regards,
Luca Boccassi


  reply	other threads:[~2020-10-27 10:59 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
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 [this message]
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=ed94167201a9730b0a54504e2bf0be8fc3a19c9f.camel@gmail.com \
    --to=luca.boccassi@gmail.com \
    --cc=openembedded-core@lists.openembedded.org \
    --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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox