From: Mark Hatle <mark.hatle@windriver.com>
To: <openembedded-core@lists.openembedded.org>
Subject: Re: Problems with PACKAGE_CLASSES = "package_tar"
Date: Wed, 24 Apr 2013 11:18:56 -0500 [thread overview]
Message-ID: <517805F0.5030501@windriver.com> (raw)
In-Reply-To: <AAE0766F5AF36B46BAB7E0EFB927320630E4A540CC@GBTWK10E001.Technology.local>
On 4/24/13 10:58 AM, Lewis, Nick wrote:
> I am seeing problems when using PACKAGE_CLASSES = "package_tar"
>
> There are many warnings about python indents and there are errors regarding
> missing populate_sdk_tar.bbclass and rootfs_tar.bbclass
I don't believe that package class has been updated in a while. It's not one of
the normal testing ones.
ipk, rpm and the two most used. deb is also available, but at least in the past
has had issues in a few places. (I think those are all resolved now.)
--Mark
> --
>
> Nick
>
> *Nick Lewis*
>
> nick.lewis@usa.g4s.com <mailto:nick.lewis@usa.g4s.com>
>
> +44 1684 277137 <tel:+441684277137>
>
> www.g4stechnology.com <http://www.g4stechnology.com/>
>
> New Challenge House, International Drive, Tewkesbury, Gloucestershire, GL20 8UQ, UK
>
> **
>
> *P**Please consider the environment before printing this email***
>
>
> --------------------------------------------------------------------------------
> The details of this company are as follows:
> G4S Technology Limited, Registered Office: Challenge House, International Drive,
> Tewkesbury, Gloucestershire GL20 8UQ, Registered in England No. 2382338.
>
> This communication may contain information which is confidential, personal
> and/or privileged.
>
> It is for the exclusive use of the intended recipient(s).
> If you are not the intended recipient(s), please note that any distribution,
> forwarding, copying or use of this communication or the information in it is
> strictly prohibited.
>
> Any personal views expressed in this e-mail are those of the individual sender
> and the company does not endorse or accept responsibility for them.
>
> Prior to taking any action based upon this e-mail message, you should seek
> appropriate confirmation of its authenticity.
>
> This e-mail has been scanned for all viruses by MessageLabs.
>
>
> _______________________________________________
> Openembedded-core mailing list
> Openembedded-core@lists.openembedded.org
> http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/openembedded-core
>
next prev parent reply other threads:[~2013-04-24 16:36 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-04-24 15:58 Problems with PACKAGE_CLASSES = "package_tar" Lewis, Nick
2013-04-24 16:18 ` Mark Hatle [this message]
2013-04-24 16:28 ` Richard Purdie
2013-04-24 16:57 ` Otavio Salvador
2013-04-25 7:29 ` Lewis, Nick
2013-04-25 10:21 ` Lewis, Nick
2013-04-25 12:00 ` Otavio Salvador
2013-04-25 17:05 ` Paul Eggleton
2013-04-25 18:21 ` Burton, Ross
2013-04-25 12:19 ` Richard Purdie
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=517805F0.5030501@windriver.com \
--to=mark.hatle@windriver.com \
--cc=openembedded-core@lists.openembedded.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