From: Richard Purdie <richard.purdie@linuxfoundation.org>
To: "Lewis, Nick" <nick.lewis@usa.g4s.com>
Cc: "'openembedded-core@lists.openembedded.org'"
<openembedded-core@lists.openembedded.org>
Subject: Re: Problems with PACKAGE_CLASSES = "package_tar"
Date: Thu, 25 Apr 2013 13:19:57 +0100 [thread overview]
Message-ID: <1366892397.29677.56.camel@ted> (raw)
In-Reply-To: <AAE0766F5AF36B46BAB7E0EFB927320630E4A540D1@GBTWK10E001.Technology.local>
On Thu, 2013-04-25 at 11:21 +0100, 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
> >
> >With 1.3 (danny)? These should be fixed in 1.4 (dyland) and master...
>
> Richard
> I have tried cherry picking from Dylan but it also seems to be missing populate_sdk_tar.bbclass and rootfs_tar.bbclass
> Does Dylan support PACKAGE_CLASSES = "package_tar" without these classes?
The package_tar class generates tarballs. tarballs do not have
dependency information so its not possible to implement the
populate_sdk_tar or rootfs_tar classes on top of it.
I'm seriously considering removing the package_tar code since it isn't
really useful and its clear nobody uses it since it remained broken for
a long time.
What you probably want to do is use a low overhead package manager like
opkg, then after image generation remove the package data.
core-image-minimal is an example of an image which does this.
Cheers,
Richard
prev parent reply other threads:[~2013-04-25 12:38 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
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 [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=1366892397.29677.56.camel@ted \
--to=richard.purdie@linuxfoundation.org \
--cc=nick.lewis@usa.g4s.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