From: "Marc Reilly" <marc@cpdesign.com.au>
To: "'Paul Eggleton'" <paul.eggleton@linux.intel.com>
Cc: openembedded-core@lists.openembedded.org
Subject: Re: Add recipe for hplip 3.12.6
Date: Mon, 20 Aug 2012 23:48:30 +1000 [thread overview]
Message-ID: <00a401cd7eda$7e0d65f0$7a2831d0$@cpdesign.com.au> (raw)
In-Reply-To: <1657652.otRuZizLvo@helios>
Hi,
> > This is based on a recipe for an earlier version which didn't seem to
> > make it into oe-core. I'm guessing that oe-core is the correct place for
it:
> > next to cups, ghostscript and foomatic.
>
> Since this is something that not everyone needs I think the best place for
it is
> probably meta-oe. I believe the justification for having cups etc.
available in
> OE-Core is that these are required when you want LSB compliance.
Fair enough, I'll respin it for meta-oe.
Cheers,
Mare
prev parent reply other threads:[~2012-08-20 14:00 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-08-20 0:21 Add recipe for hplip 3.12.6 Marc Reilly
2012-08-20 0:21 ` [PATCH] hplip: Introduce version 3.12.6 Marc Reilly
2012-08-20 13:31 ` Add recipe for hplip 3.12.6 Paul Eggleton
2012-08-20 13:48 ` Marc Reilly [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='00a401cd7eda$7e0d65f0$7a2831d0$@cpdesign.com.au' \
--to=marc@cpdesign.com.au \
--cc=openembedded-core@lists.openembedded.org \
--cc=paul.eggleton@linux.intel.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox