All of lore.kernel.org
 help / color / mirror / Atom feed
From: Koen Kooi <k.kooi@student.utwente.nl>
To: angstrom-distro-devel@linuxtogo.org
Cc: openembedded-devel@openembedded.org
Subject: Re: [Angstrom-devel] RFC: Add ipkg to minimal image
Date: Sun, 02 Dec 2007 20:13:17 +0100	[thread overview]
Message-ID: <475303CD.2080401@student.utwente.nl> (raw)
In-Reply-To: <1196616132.6648.20.camel@localhost.localdomain>

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Richard Purdie schreef:
> On Sun, 2007-12-02 at 16:35 +0100, Koen Kooi wrote:
>> To make it a bit more clear:
>>
>> There are 3 seperate items being discusses here:
>>
>>  1. how to stop a packagemanager getting into an image
>>  2. selecting which packageformat the build should use
>>  3. selecting which packagemanager handles which packageformat (ipkg can
>> handle .debs for example)
> 
> An image built with rootfs_deb needs to dpkg+apt, an image built with
> rootfs_ipk needs to use ipkg. The two will not currently work the other
> way around.

You can use rootfs_ipk to build a rootfs from .debs. ipkg only cares
about the files being an ar-wrapped-tarball, not the suffix. It requires
a small changes to the bbclass, but it is possible.

regards,

Koen

> Until that is addressed, points 2 and 3 are the same thing.
> 
>> ANGSTROM_PKG_FORMAT handles 2. and 3., but not 1. (yet)
> 
> The setting of IMG_PKGTYPE used or the inherit order of the package
> classes determine this. Do we need the angstrom specific variable?
> 
>> I think having a flag indicating *which* packagemanager gets is (like
>> Rods patch does) is a good thing, but a flag toggling the presence of
>> the packagemanager wouldn't be, since you can't distinguish the
>> resulting images from each other.
>> I think creating e.g. <foo>-nopm.bb recipes that do 'require <foo>.bb ;
>> PACKAGE_MANAGER = " "' would be the least confusing option.
> 
> I agree that specific images should have specific feature sets. This
> comes back to my point about the machine=nslu2 needing to make the
> console image usable.
> 
> Has anyone looked at how Poky does its IMAGE_FEATURES magic (see
> poky-image.bbclass)? Adding package-manager as an IMAGE_FEATURE style
> option and not as a DISTRO_FEATURE as I previously suggested could
> perhaps be a way forward...
> 
> Cheers,
> 
> Richard
> 
> 
> 
> _______________________________________________
> Angstrom-distro-devel mailing list
> Angstrom-distro-devel@linuxtogo.org
> http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/angstrom-distro-devel
> 


- --
koen@dominion.kabel.utwente.nl will go go away in december 2007, please
use k.kooi@student.utwente.nl instead.

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.5 (Darwin)

iD8DBQFHUwPNMkyGM64RGpERArb0AJ49JilRuw6f/Tj2VZ0VAJ5K52XWMACfdqKe
glVjhPyQNEeBOPy7MjHFDIM=
=r8/t
-----END PGP SIGNATURE-----



  reply	other threads:[~2007-12-02 19:16 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-12-02  1:18 RFC: Add ipkg to minimal image Rod Whitby
2007-12-02  3:57 ` Rod Whitby
2007-12-02  8:17   ` [Angstrom-devel] " Koen Kooi
2007-12-02 10:08     ` Rod Whitby
2007-12-02 11:31     ` Richard Purdie
2007-12-02 12:54       ` Holger Freyther
2007-12-02 13:17       ` Koen Kooi
2007-12-02 15:35         ` Koen Kooi
2007-12-02 17:22           ` Richard Purdie
2007-12-02 19:13             ` Koen Kooi [this message]
2007-12-02 18:45       ` Marcin Juszkiewicz
2007-12-02 18:17 ` Paul Sokolovsky
2007-12-02 20:52   ` Rod Whitby
2007-12-03 15:21     ` Leon Woestenberg
2007-12-04  0:07       ` Rod Whitby

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=475303CD.2080401@student.utwente.nl \
    --to=k.kooi@student.utwente.nl \
    --cc=angstrom-distro-devel@linuxtogo.org \
    --cc=openembedded-devel@lists.openembedded.org \
    --cc=openembedded-devel@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 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.