From: Philip Balister <philip@balister.org>
To: openembedded-devel@lists.openembedded.org
Subject: Re: [meta-oe 1/1] lxc : Add recipe for building Linux Containers tools.
Date: Thu, 03 May 2012 06:59:43 -0400 [thread overview]
Message-ID: <4FA2651F.3030701@balister.org> (raw)
In-Reply-To: <jnrvsr$4jc$1@dough.gmane.org>
On 05/02/2012 02:54 PM, Koen Kooi wrote:
> Op 02-05-12 19:45, Philip Balister schreef:
>> Linux containers are a lightweight virtualization system.
>
>> Compile tested on F15 and lightly run tested on a pandaboard.
>
>> Signed-off-by: Philip Balister <philip@balister.org> ---
>> meta-oe/recipes-extended/lxc/lxc_git.bb | 21 +++++++++++++++++++++ 1
>> files changed, 21 insertions(+), 0 deletions(-) create mode 100644
>> meta-oe/recipes-extended/lxc/lxc_git.bb
>
>> diff --git a/meta-oe/recipes-extended/lxc/lxc_git.bb
>> b/meta-oe/recipes-extended/lxc/lxc_git.bb new file mode 100644 index
>> 0000000..8f22e77 --- /dev/null +++
>> b/meta-oe/recipes-extended/lxc/lxc_git.bb @@ -0,0 +1,21 @@ +SUMMARY =
>> "Linux Containers tools" +DESCRIPTION = "Linux containers are a light
>> weight isolation system for Linux." +HOMEPAGE =
>> "http://lxc.sourceforge.net" +LICENSE = "LGPLv2.1"
>
> Move LIC_FILES_CHKSUM to here
>
>> + +PV = "0.8.0-rc2"
>
> That violates the versioning policy
>
>> + +RDEPENDS_${PN} = "perl perl-modules"
>
> That needs to go below do_install() and specify the actual modules it needs,
> not the blanket meta-package.
>
I agree, but I ran out of time messing with it. It looks like the
RDEPENDS are not set for perl modules, so you need to list them all.
There is one perl script in the lxc utilities that imports one perl
module. This module imports another, rinse lather repeat. I gave up and
sucked in the whole mess so I could get work done.
I'll gladly make a note this is not optimal in the commit message. I
doubt lsc will become super popular on embedded systems, and when it
does we can clean up the perl modules.
> Speaking of lxc, have you tried systemd-nspawn to launch containers yet?
Not yet. Still trying to get my head around the whole concept. One step
at a time.
Philip
>
> regards,
>
> Koen
_______________________________________________
Openembedded-devel mailing list
Openembedded-devel@lists.openembedded.org
http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/openembedded-devel
next prev parent reply other threads:[~2012-05-03 11:09 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-05-02 17:45 [meta-oe 0/1] Linux Containers recipe Philip Balister
2012-05-02 17:45 ` [meta-oe 1/1] lxc : Add recipe for building Linux Containers tools Philip Balister
2012-05-02 18:54 ` Koen Kooi
2012-05-03 10:59 ` Philip Balister [this message]
2012-05-07 17:40 ` Philip Balister
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=4FA2651F.3030701@balister.org \
--to=philip@balister.org \
--cc=openembedded-devel@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