All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Robert P. J. Day" <rpjday@crashcourse.ca>
To: Paul Eggleton <paul.eggleton@linux.intel.com>
Cc: yocto@yoctoproject.org
Subject: Re: what is the future for package_tar.bbclass?
Date: Tue, 20 Jan 2015 05:04:54 -0500 (EST)	[thread overview]
Message-ID: <alpine.LFD.2.11.1501200503470.7100@localhost> (raw)
In-Reply-To: <2608332.CqdSeLLBDo@peggleto-mobl5.ger.corp.intel.com>

On Tue, 20 Jan 2015, Paul Eggleton wrote:

> On Monday 19 January 2015 22:57:37 Rifenbark, Scott M wrote:
> > The class is broken and unsupported.  I have updated the docs indicating
> > such.
>
> I'm not sure that's true. It's not supported for building images,
> and it never has been. However it can be used for producing tarball
> packages for individual recipes.

  i have no strong feelings either way, i was just repeating an
observation of mine from a while back that the tar packaging seemed to
get precious little attention compared to the three "standard"
packaging formats.

rday

-- 

========================================================================
Robert P. J. Day                                 Ottawa, Ontario, CANADA
                        http://crashcourse.ca

Twitter:                                       http://twitter.com/rpjday
LinkedIn:                               http://ca.linkedin.com/in/rpjday
========================================================================


      reply	other threads:[~2015-01-20 10:05 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-01-10 15:16 what is the future for package_tar.bbclass? Robert P. J. Day
2015-01-19 22:57 ` Rifenbark, Scott M
2015-01-20  8:43   ` Paul Eggleton
2015-01-20 10:04     ` Robert P. J. Day [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=alpine.LFD.2.11.1501200503470.7100@localhost \
    --to=rpjday@crashcourse.ca \
    --cc=paul.eggleton@linux.intel.com \
    --cc=yocto@yoctoproject.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.