package installed_size field

package installed_size field

[Jens Erdmann]

Hi folks,

I have a question in package creation. In my build process i create ipkg 
packages and i don't understand, how the installed_size has to be 
detected and where it will be set. My first idea were the 
package_ipkg.bbclass but it's missing there. How do you manage this?


-- 
------- ROAD ...the handyPC Company - - -  ) ) )

Jens Erdmann
Software Development

ROAD GmbH
Bennigsenstr. 14 | 12159 Berlin | Germany
fon: +49 (30) 230069 - 64 | fax: +49 (30) 230069 - 69
url: www.road.de

Amtsgericht Charlottenburg: HRB 96688 B
Managing director: Hans-Peter Constien

Re: package installed_size field

[Koen Kooi]

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

On 23-04-10 16:41, Jens Erdmann wrote:
> Hi folks,
> 
> I have a question in package creation. In my build process i create ipkg
> packages and i don't understand, how the installed_size has to be
> detected and where it will be set. My first idea were the
> package_ipkg.bbclass but it's missing there. How do you manage this?

Historically we don't handle this, because in opkg "installed_size" is
not tightly defined, so when installing it on e.g. compressed ubifs the
*actual* installed size is usually less than the size on e.g. ext2. The
fear was that package managers would refuse to install e.g. a 30MB text
file when ubifs reports 29MB free, even if that file would only occupy
3MB of actual space.

That's the background, I personally would like to include that (the
"uncompressed image size") info in the package, but I am unsure what the
implications are of that when using a recent opkg.

regards,

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

iD8DBQFL0b7JMkyGM64RGpERAte3AJ4l7aa8lcrl5GqjNgAYwLJTFLo06ACgnuxZ
ivi3OMdwFFDpAzQcPZNH054=
=qSJ6
-----END PGP SIGNATURE-----