Openembedded Core Discussions
 help / color / mirror / Atom feed
From: Richard Purdie <richard.purdie@linuxfoundation.org>
To: "Robert P. J. Day" <rpjday@crashcourse.ca>
Cc: OE Core mailing list <openembedded-core@lists.openembedded.org>
Subject: Re: [PATCH] Mention package_tar packaging in local.conf.sample
Date: Thu, 24 Jul 2014 13:08:12 +0100	[thread overview]
Message-ID: <1406203692.27697.6.camel@ted> (raw)
In-Reply-To: <alpine.LFD.2.11.1407240509150.1086@localhost>

On Thu, 2014-07-24 at 05:10 -0400, Robert P. J. Day wrote:
> Signed-off-by: Robert P. J. Day <rpjday@crashcourse.ca>
> 
> ---
> 
>   is this the appropriate comment for tarball packaging?
> 
> diff --git a/meta/conf/local.conf.sample b/meta/conf/local.conf.sample
> index 555f8db..a200002 100644
> --- a/meta/conf/local.conf.sample
> +++ b/meta/conf/local.conf.sample
> @@ -78,7 +78,8 @@ MACHINE ??= "qemux86"
>  #  - 'package_deb' for debian style deb files
>  #  - 'package_ipk' for ipk files are used by opkg (a debian style embedded package manager)
>  #  - 'package_rpm' for rpm style packages
> -# E.g.: PACKAGE_CLASSES ?= "package_rpm package_deb package_ipk"
> +#  - 'package_tar' for tarball packages
> +# E.g.: PACKAGE_CLASSES ?= "package_rpm package_deb package_ipk package_tar"
>  # We default to ipk:
>  PACKAGE_CLASSES ?= "package_ipk"
> 

The class is pretty useless, lets leave this one less documented ;-)

I keep thinking we should delete it instead to be honest...

Cheers,

Richard



      parent reply	other threads:[~2014-07-24 12:08 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-07-24  9:10 [PATCH] Mention package_tar packaging in local.conf.sample Robert P. J. Day
2014-07-24  9:16 ` Burton, Ross
2014-07-24  9:18   ` Robert P. J. Day
2014-07-24  9:59   ` Paul Eggleton
2014-07-24 12:08 ` Richard Purdie [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=1406203692.27697.6.camel@ted \
    --to=richard.purdie@linuxfoundation.org \
    --cc=openembedded-core@lists.openembedded.org \
    --cc=rpjday@crashcourse.ca \
    /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