All of lore.kernel.org
 help / color / mirror / Atom feed
From: claus.stovgaard@gmail.com
To: Khem Raj <raj.khem@gmail.com>,
	OpenEmbedded Devel List
	<openembedded-devel@lists.openembedded.org>
Cc: nerdboy@gentoo.org
Subject: Re: [meta-oe]
Date: Wed, 22 Dec 2021 11:39:28 +0100	[thread overview]
Message-ID: <e9544ca1366bb22836bc167c20a3249f1151e36e.camel@gmail.com> (raw)
In-Reply-To: <b0fc66bb-db59-11df-9eb9-a11718062af7@gmail.com>

On Tue, 2021-12-21 at 18:44 -0800, Khem Raj wrote:
> 
> On 12/21/21 2:04 PM, Claus Stovgaard wrote:
> > Hi Khem.
> > 
> > Thanks for your reply
> > 
> > On Mon, 2021-12-20 at 20:15 -0800, Khem Raj wrote:
> > > 
> > > On 12/20/21 1:37 PM, Claus Stovgaard wrote:
> > > > Looking forward to feedback on this.
> > > > 
> > > > Do you prefer to include patch text in the request-pull?
> > > 
> > > this looks good. Also check at layers.openembedded.org to see if
> > > some
> > > other layer is maintaining them already. If not then send it as
> > > patches
> > 
> > usbip-tools and gutenprint is not provided by any other layers as
> > far
> > as I can see.
> > 
> > pycups is also available in meta-printing.
> > https://github.com/rossburton/meta-printing
> > 
> > Though it seems to be discontinued, and only support zeus and
> > dunfell
> > so would significant work to get updated. Though it might be
> > relevant.
> > Have added Steve Arnold to the list (maintainer for meta-printing). 
> > so
> > he can comment about the status of meta-printing.
> 
> To be honest, meta-printing seems better suited for these recipes 
> provided layer is maintained still. Dunfell is LTS release and well 
> maintained so I would not consider is dead by any means. I would like
> to 
> hear from Steve and see what his plans are for this layer.
> 

I agree for gutenprint and pycups.

Though for usbip-tools, being a generic userspace tool part of the
linux kernel like perf I think it should be part of meta-openembedded
or poky.
I used it for more than 10 years ago to access USB jtag and other USB
things, so was a bit puzzeled that it was not already in poky / meta-
openembedded.

Back to meta-printing - if Steve is up for review the changes I can
help with getting meta-printing up to speed. Both for dunfell, and
prepare for kirkstone.

Also I don't know if Ross Burton should be involved - as the layer is
hosted on his github profile, or if Steve is handling the meta-
printing.

Regards
Claus



      reply	other threads:[~2021-12-22 10:39 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-12-20 21:37 [meta-oe] Claus Stovgaard
2021-12-21  4:15 ` [meta-oe] Khem Raj
2021-12-21 22:04   ` [meta-oe] Claus Stovgaard
2021-12-22  2:44     ` [meta-oe] Khem Raj
2021-12-22 10:39       ` claus.stovgaard [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=e9544ca1366bb22836bc167c20a3249f1151e36e.camel@gmail.com \
    --to=claus.stovgaard@gmail.com \
    --cc=nerdboy@gentoo.org \
    --cc=openembedded-devel@lists.openembedded.org \
    --cc=raj.khem@gmail.com \
    /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.