Write a packaging systems on mobile and embedded Linux systems lecture.

Thu, 05 Jan 2012 19:42:10 +0100

author
Michael Schloh von Bennewitz <michael@schloh.com>
date
Thu, 05 Jan 2012 19:42:10 +0100
changeset 7
3c966c183dea
parent 6
4b9e0438a53c
child 8
74cb68a698cf

Write a packaging systems on mobile and embedded Linux systems lecture.
This revision is only an outline of what will eventually be a well
rehearsed, fully developed lecture with media and klim bim.

packaging/embeddedpkg.txt file | annotate | diff | comparison | revisions
     1.1 --- /dev/null	Thu Jan 01 00:00:00 1970 +0000
     1.2 +++ b/packaging/embeddedpkg.txt	Thu Jan 05 19:42:10 2012 +0100
     1.3 @@ -0,0 +1,110 @@
     1.4 +Mobile and Embedded Linux Packaging Systems
     1.5 +Audience: Mobile and embedded linux developers
     1.6 +Duration: 45 minute presentation
     1.7 +
     1.8 +Author and Speaker
     1.9 +------------------
    1.10 +Michael Schloh von Bennewitz
    1.11 +Software Engineer, Europalab Networks
    1.12 +web: http://michael.schloh.com/
    1.13 +email: michael@schloh.com
    1.14 +isdn: +49(89)44239885
    1.15 +voip: sips:michael@schloh.com
    1.16 +xmpp: MSvB
    1.17 +
    1.18 +Main chapters (20 minutes)
    1.19 +--------------------------
    1.20 +  Concepts
    1.21 +    Definition of packaging
    1.22 +      Software, text, metadata, other data
    1.23 +      Anatomy of various package types
    1.24 +      Mock up package diagram
    1.25 +    History of packaging
    1.26 +      SVR5
    1.27 +      DEB
    1.28 +      RPM
    1.29 +      Bundle
    1.30 +      Ports
    1.31 +      IPkg
    1.32 +      OPkg
    1.33 +      APK
    1.34 +    Dependency resolution
    1.35 +    Binary or source packages
    1.36 +    Automated package management
    1.37 +
    1.38 +  Requirements
    1.39 +    Mobile and embedded packaging defined
    1.40 +    Performance constraints
    1.41 +    Signing and security
    1.42 +    Hardware choices
    1.43 +      ARM, PC Engines, Panda/Beagle board, Chumby...
    1.44 +    Affecting design choices
    1.45 +
    1.46 +  Commercial aspects
    1.47 +    Trend of online package stores
    1.48 +    Big five (Google, Intel, Nokia, Microsoft, Apple)
    1.49 +    Balancing developer interest with beaurocratic apathy
    1.50 +      Paying money to become an 'official' developer
    1.51 +      Being 'allowed' to develop own applications
    1.52 +      Choice of license, ownership, and business models
    1.53 +      Unwanted nontechnical involvement
    1.54 +
    1.55 +  Case studies
    1.56 +    Android [1]
    1.57 +    OpenWRT [2]
    1.58 +    M0n0wall [3]
    1.59 +    Harmattan [4]
    1.60 +    WetabOS [5]
    1.61 +    Opendreambox [6]
    1.62 +    Tizen [7][8]
    1.63 +
    1.64 +Demonstrations (10 minutes)
    1.65 +---------------------------
    1.66 +  WetabOS on ExoPC hardware (RPM)
    1.67 +  Harmattan on Nokia mobil phone (DEB)
    1.68 +  Opendreambox on Dream set-top box (I/OPKG)
    1.69 +
    1.70 +Optional discussion (5 minutes)
    1.71 +-------------------------------
    1.72 +  Legacy MeeGo packaging
    1.73 +  Intel AppUp approach
    1.74 +  Packaging Arduino software
    1.75 +
    1.76 +Questions (10 minutes)
    1.77 +---------------------
    1.78 +  Anticipated questions
    1.79 +    How to make a package for a given embedded OS?
    1.80 +    Can a package be prepared on one device and copied to another?
    1.81 +    Can packages be prepared for various architectures with fat binaries?
    1.82 +    Architectural hardware 32-bit, 64-bit, and other CPU properties.
    1.83 +    How do I know which packages are installed on my device or phone?
    1.84 +
    1.85 +Relevant jokes about...
    1.86 +-----------------------
    1.87 +  Packaging systems
    1.88 +  Linux operating system
    1.89 +
    1.90 +Glossary
    1.91 +--------
    1.92 +  Debian package file (DEB)
    1.93 +  Redhat Package Manager (RPM)
    1.94 +  Android Application Package File (APK)
    1.95 +  Silverlight Application Package (XAP)
    1.96 +
    1.97 +Errata
    1.98 +------
    1.99 +  Android is not considered Linux by some.
   1.100 +  M0n0wall does not really run on Linux, rather on FreeBSD.
   1.101 +  Competing 'big five' do not all develop or distribute Linux.
   1.102 +  Some technology is deprecated, for example MeeGo variants.
   1.103 +
   1.104 +Links and notes
   1.105 +---------------
   1.106 +  [1] http://developer.android.com/guide/developing/building/
   1.107 +  [2] http://www.openwrt.org/
   1.108 +  [3] http://m0n0.ch/wall/
   1.109 +  [4] http://harmattan-dev.nokia.com/docs/library/
   1.110 +  [5] http://www.4tiitoo.com/wetab-os.en.html
   1.111 +  [6] http://www.dreamboxupdate.com/
   1.112 +  [7] http://www.tizen.org/
   1.113 +  [8] will be considered a valid topic pending advice from Intel reps.

mercurial