# HG changeset patch # User Michael Schloh von Bennewitz # Date 1326479022 -3600 # Node ID 642096a4a05e5c7392f51c85a3b58bbd06235b32 # Parent 8b5e50e4968e5c292be8b0eac8a6b89b938521dd Changed name from 'embeddedpkg' to more specific 'embedlinuxpkg'. diff -r 8b5e50e4968e -r 642096a4a05e packaging/embeddedpkg.txt --- a/packaging/embeddedpkg.txt Fri Jan 13 19:15:33 2012 +0100 +++ /dev/null Thu Jan 01 00:00:00 1970 +0000 @@ -1,110 +0,0 @@ -Mobile and Embedded Linux Packaging Systems -Audience: Mobile and embedded linux developers -Duration: 45 minute presentation - -Author and Speaker ------------------- -Michael Schloh von Bennewitz -Software Engineer, Europalab Networks -web: http://michael.schloh.com/ -email: michael@schloh.com -isdn: +49(89)44239885 -voip: sips:michael@schloh.com -xmpp: MSvB - -Main chapters (20 minutes) --------------------------- - Concepts - Definition of packaging - Software, text, metadata, other data - Anatomy of various package types - Mock up package diagram - History of packaging - SVR5 - DEB - RPM - Bundle - Ports - IPkg - OPkg - APK - Dependency resolution - Binary or source packages - Automated package management - - Requirements - Mobile and embedded packaging defined - Performance constraints - Signing and security - Hardware choices - ARM, PC Engines, Panda/Beagle board, Chumby... - Affecting design choices - - Commercial aspects - Trend of online package stores - Big five (Google, Intel, Nokia, Microsoft, Apple) - Balancing developer interest with beaurocratic apathy - Paying money to become an 'official' developer - Being 'allowed' to develop own applications - Choice of license, ownership, and business models - Unwanted nontechnical involvement - - Case studies - Android [1] - OpenWRT [2] - M0n0wall [3] - Harmattan [4] - WetabOS [5] - Opendreambox [6] - Tizen [7][8] - -Demonstrations (10 minutes) ---------------------------- - WetabOS on ExoPC hardware (RPM) - Harmattan on Nokia mobil phone (DEB) - Opendreambox on Dream set-top box (I/OPKG) - -Optional discussion (5 minutes) -------------------------------- - Legacy MeeGo packaging - Intel AppUp approach - Packaging Arduino software - -Questions (10 minutes) ---------------------- - Anticipated questions - How to make a package for a given embedded OS? - Can a package be prepared on one device and copied to another? - Can packages be prepared for various architectures with fat binaries? - Architectural hardware 32-bit, 64-bit, and other CPU properties. - How do I know which packages are installed on my device or phone? - -Relevant jokes about... ------------------------ - Packaging systems - Linux operating system - -Glossary --------- - Debian package file (DEB) - Redhat Package Manager (RPM) - Android Application Package File (APK) - Silverlight Application Package (XAP) - -Errata ------- - Android is not considered Linux by some. - M0n0wall does not really run on Linux, rather on FreeBSD. - Competing 'big five' do not all develop or distribute Linux. - Some technology is deprecated, for example MeeGo variants. - -Links and notes ---------------- - [1] http://developer.android.com/guide/developing/building/ - [2] http://www.openwrt.org/ - [3] http://m0n0.ch/wall/ - [4] http://harmattan-dev.nokia.com/docs/library/ - [5] http://www.4tiitoo.com/wetab-os.en.html - [6] http://www.dreamboxupdate.com/ - [7] http://www.tizen.org/ - [8] will be considered a valid topic pending advice from Intel reps.