DOCSLIB.ORG

Yocto Project Reference Manual Is for the 1.6.3 Release of the Yocto Project

Total Page：16

File Type：pdf, Size：1020Kb

Download full-text PDF Read full-text
Yocto Project Reference Manual Is for the 1.6.3 Release of the Yocto Project Richard Purdie, Linux Foundation <[email protected]> by Richard Purdie Copyright © 2010-2015 Linux Foundation Permission is granted to copy, distribute and/or modify this document under the terms of the Creative Commons Attribution-Share Alike 2.0 UK: England & Wales [http://creativecommons.org/licenses/by-sa/2.0/uk/] as published by Creative Commons. Manual Notes • This version of the Yocto Project Reference Manual is for the 1.6.3 release of the Yocto Project. To be sure you have the latest version of the manual for this release, go to the Yocto Project documentation page [http://www.yoctoproject.org/documentation] and select the manual from that site. Manuals from the site are more up-to-date than manuals derived from the Yocto Project released TAR files. • If you located this manual through a web search, the version of the manual might not be the one you want (e.g. the search might have returned a manual much older than the Yocto Project version with which you are working). You can see all Yocto Project major releases by visiting the Releases [https://wiki.yoctoproject.org/wiki/Releases] page. If you need a version of this manual for a different Yocto Project release, visit the Yocto Project documentation page [http://www.yoctoproject.org/ documentation] and select the manual set by using the "ACTIVE RELEASES DOCUMENTATION" or "DOCUMENTS ARCHIVE" pull-down menus. • To report any inaccuracies or problems with this manual, send an email to the Yocto Project discussion group at [email protected] or log into the freenode #yocto channel. Table of Contents 1. Introduction ............................................................................................................................ 1 1.1. Introduction ................................................................................................................. 1 1.2. Documentation Overview ............................................................................................. 1 1.3. System Requirements .................................................................................................. 1 1.3.1. Supported Linux Distributions ........................................................................... 2 1.3.2. Required Packages for the Host Development System ....................................... 2 1.3.3. Required Git, tar, and Python Versions .............................................................. 5 1.4. Obtaining the Yocto Project ......................................................................................... 6 1.5. Development Checkouts .............................................................................................. 7 2. Using the Yocto Project .......................................................................................................... 8 2.1. Running a Build ........................................................................................................... 8 2.1.1. Build Overview ................................................................................................. 8 2.1.2. Building an Image Using GPL Components ........................................................ 8 2.2. Installing and Using the Result .................................................................................... 8 2.3. Debugging Build Failures ............................................................................................. 9 2.3.1. Task Failures ..................................................................................................... 9 2.3.2. Running Specific Tasks ...................................................................................... 9 2.3.3. Dependency Graphs ....................................................................................... 10 2.3.4. General BitBake Problems ............................................................................... 10 2.3.5. Development Host System Issues ................................................................... 10 2.3.6. Building with No Dependencies ....................................................................... 10 2.3.7. Variables ........................................................................................................ 10 2.3.8. Recipe Logging Mechanisms ........................................................................... 11 2.3.9. Other Tips ...................................................................................................... 12 2.4. Maintaining Build Output Quality ............................................................................... 12 2.4.1. Enabling and Disabling Build History ............................................................... 12 2.4.2. Understanding What the Build History Contains ............................................... 13 3. A Closer Look at the Yocto Project Development Environment ............................................... 17 3.1. User Configuration ..................................................................................................... 18 3.2. Metadata, Machine Configuration, and Policy Configuration ........................................ 19 3.2.1. Distro Layer .................................................................................................... 21 3.2.2. BSP Layer ....................................................................................................... 21 3.2.3. Software Layer ............................................................................................... 21 3.3. Sources ..................................................................................................................... 22 3.3.1. Upstream Project Releases .............................................................................. 23 3.3.2. Local Projects ................................................................................................. 23 3.3.3. Source Control Managers (Optional) ................................................................ 24 3.3.4. Source Mirror(s) .............................................................................................. 24 3.4. Package Feeds ........................................................................................................... 24 3.5. BitBake ...................................................................................................................... 25 3.5.1. Source Fetching .............................................................................................. 26 3.5.2. Patching ......................................................................................................... 27 3.5.3. Configuration and Compilation ........................................................................ 28 3.5.4. Package Splitting ............................................................................................ 29 3.5.5. Image Generation ........................................................................................... 31 3.5.6. SDK Generation .............................................................................................. 33 3.6. Images ...................................................................................................................... 34 3.7. Application Development SDK .................................................................................... 35 4. Technical Details .................................................................................................................. 37 4.1. Yocto Project Components ......................................................................................... 37 4.1.1. BitBake ........................................................................................................... 37 4.1.2. Metadata (Recipes) ......................................................................................... 38 4.1.3. Classes ........................................................................................................... 38 4.1.4. Configuration .................................................................................................. 38 4.2. Cross-Development Toolchain Generation ................................................................... 38 4.3. Shared State Cache ................................................................................................... 41 4.3.1. Overall Architecture ........................................................................................ 41 4.3.2. Checksums (Signatures) ................................................................................. 41 4.3.3. Shared State .................................................................................................. 43 4.3.4. Tips and Tricks ................................................................................................ 44 4.4. x32 ........................................................................................................................... 45 iii Yocto Project Reference Manual 4.4.1. Support .......................................................................................................... 45 4.4.2. Completing x32 .............................................................................................. 45 4.4.3. Using x32 Right Now ...................................................................................... 46 4.5. Wayland .................................................................................................................... 46 4.5.1. Support .........................................................................................................
Load more

Recommended publications
  • 27Th Annual Florida Sale
    ALEX LYON & SON SALES MANAGERS & AUCTIONEERS proudly present the 27TH ANNUAL FLORIDA SALE KISSIMMEE (WINTER GARDEN), FLORIDA SATURDAY, FEBRUARY 1 - SUNDAY, FEBRUARY 9 at 9:00 AM THE GREATEST SALE OF THE YEAR! 9 DAYS OF SELLING! 27TH ANNUAL RENTAL RETURNS AUCTION Construction Equipment, Aerials, Forklifts, Cranes, Dump Trucks, Truck Tractors, Trailers, Support & Attachments. SALES MANAGERS & AUCTIONEERS AHERN RENTALS 2020 BID KISSIMMEE, FLORIDA BID ONLINE SAT., FEBRUARY 1 - SUN., FEBRUARY 9 at 9:00 AM ONLINE SPECIAL ANNOUNCEMENT: ONLINE BIDDING AVAILABLE DAYS 3-9 ONLY! ADDRESS: 12601 Avalon Road, Winter Garden, Florida 34787. JACK’S NOTE: 27 Glorious Years Conducting This High Quality Sale. FLORIDA AUCTIONEER: AU-1548 Jack Lyon. FLORIDA LICENSE: #AB-1091. SALE SITE PHONE: (407) 239-2700. ✭ SPECIAL NOTE ✭ For Non-Resident US Bidders: A $10,000 Cashier’s Check Deposited Prior To Bidding Will Be Required. ✭ NO EXCEPTIONS ✭ TERMS & CONDITIONS: “Cash or Company Check” accompanied by current “Bank Letter of Guarantee”, made payable to Alex Lyon & Son. Everything Sells “AS IS, WHERE IS.” The following charges will apply on all purchases: (1.) For each unit $35,001.00 and above, a 5.95% administration fee will be assessed when paying with cash or good check. (The standard fee of 8.95% will be assessed when paying with credit card); and (2.) For each unit $1,001- $35,000, a 10% administration fee will be assessed when paying with cash or good check, and a 13% fee will be assessed when paying with credit card. (3.) For each unit $0- $1,000, a 12.5% administration fee will be assessed when paying with cash or good check, and a 15.5% fee will be assessed when paying with credit card.
    [Show full text]
  • Aesthetically Driven Design of Network Based Multi-User Instruments
    Aesthetically Driven Design of Network Based Multi-User Instruments by Curtis McKinney A thesis submitted to the faculty of Bournemouth University in partial fulfilment of the requirements for the degree of Doctor of Philosophy in the School of Design, Engineering, and Computing July 2014 This copy of the thesis has been supplied on condition that anyone who consults it is understood to recognise that its copyright rests with its author and due acknowl- edgement must always be made of the use of any material contained in, or derived from, this thesis. I Aesthetically Driven Design of Network Based Multi-User Instruments Curtis McKinney Abstract Digital networking technologies open up a new world of possibilities for mu- sic making, allowing performers to collaborate in ways not possible before. Net- work based Multi-User Instruments (NMIs) are one novel method of musical collaboration that take advantage of networking technology. NMIs are digital musical instruments that exist as a single entity instantiated over several nodes in a network and are performed simultaneously by multiple musicians in real- time. This new avenue is exciting, but it begs the question of how does one design instruments for this new medium? This research explores the use of an aesthetically driven design process to guide the design, construction, rehearsal, and performance of a series of NMIs. This is an iterative process that makes use of a regularly rehearsing and performing ensemble which serves as a test-bed for new instruments, from conception, to design, to implementation, to performance. This research includes details of several NMIs constructed in accordance with this design process.
    [Show full text]
  • FULL THROTTLE TROUBLESHOOTING HINTS Some Rare Coni'igurations May Not Be Immediately Compatible with the Pull Throttle Installer and Launcher Pro­ Grams
    FULL THROTTLE TROUBLESHOOTING HINTS Some rare coni'igurations may not be immediately compatible with the Pull Throttle installer and launcher pro­ grams. I f you are experiencing problems, we have included a num­ ber of installation alternatives that will most likely allow y ou to successfully install and run Pull Throttle . Please 1·01- low the instructions below be f ore calling LucasArts Product Support f or help, a s the y will likely solve any installation problems that y ou are experiencing. If y ou encounter difficulties while attempting to run the Pull Throttle installer, it ma y help if y ou make a boot disk and reboot y our computer before running the INSTALL.EXE. To ma ke a boot disk bef ore running the installer , run the program called hlAKEB OOT .BAT from y our Pull Throttle CD. The hlAKEBOOT. BAT is located in the SUPPORT directory on your Pull Throttle CD. To get to this directory , cha nge to y our CD- R01i drive, and, at the prompt, t ype CD SUPPORT and press ENTER . Af ter the boot disk i s completed, reboot y our computer with the boot disk in your i 'loppy boot drive (usually drive A:) and try to run the installer. If this f ails , try running the IlTSTALL. BAT file located in the SUPPORT directory on your Full Throttle CL . I1 y ou cannot run the installer even a i 'ter making a boot disk, try rebooting y our computer with the boot disk and then run this batch file to install Full Throttle .
    [Show full text]
  • National Security Reform: Problems, Progress, and Prospects
    STRATEGIC STUDIES INSTITUTE The Strategic Studies Institute (SSI) is part of the U.S. Army War College and is the strategic level study agent for issues related to national security and military strategy with emphasis on geostrate- gic analysis. The mission of SSI is to use independent analysis to conduct strategic studies that develop policy recommendations on: • Strategy, planning and policy for joint and combined employment of military forces; • Regional strategic appraisals; • The nature of land warfare; • Matters affecting the Army’s future; • The concepts, philosophy, and theory of strategy; and • Other issues of importance to the leadership of the Army. Studies produced by civilian and military analysts concern topics having strategic implications for the Army, the Department of De- fense, and the larger national security community. In addition to its studies, SSI publishes special reports on topics of special or immediate interest. These include edited proceedings of conferences and topically-oriented roundtables, expanded trip re- ports, and quick reaction responses to senior Army leaders. The Institute provides a valuable analytical capability within the Army to address strategic and other issues in support of Army par- ticipation in national security policy formulation. RETHINKING LEADERSHIP AND “WHOLE OF GOVERNMENT” NATIONAL SECURITY REFORM: PROBLEMS, PROGRESS, AND PROSPECTS Joseph R. Cerami Jeffrey A. Engel Editors May 2010 Visit our website for other free publication downloads http://www.StrategicStudiesInstitute.army.mil/ To rate this publication click here. The views expressed in this report are those of the au- thors and do not necessarily reflect the official policy or position of the Department of the Army, the De- partment of Defense, or the U.S.
    [Show full text]
  • Project Proposal Service Architecture for Multimedia Based Communication
    Seite 1/8 Project Proposal Service Architecture for Multimedia Based Communication Dipl.-Ing. Eva Brucherseifer Dipl.-Ing. Stefan Eilers 02/01/06 Contents 1.The Situation......................................................................................................................... ...............2 2.The Vision............................................................................................................................... .............2 3.Related Projects...................................................................................................................... .............4 3.1.Telepathy..................................................................................................................................... 4 3.2.MOTUIM/DesktopIntegrationSIPIM .................................................................................... ..........4 3.3.KCall.......................................................................................................................................... ..4 3.4.OpenTAPI Prototype..................................................................................... ................................5 4.OpenCDI Project: Description and Bias........................................................................ .........................5 4.1.Roadmap................................................................................................. .....................................6 5.License..........................................................................................................
    [Show full text]
  • January 2010
    SPECIAL FEATURE: 2009 FRONT LINE AWARDS VOL17NO1JANUARY2010 THE LEADING GAME INDUSTRY MAGAZINE 1001gd_cover_vIjf.indd 1 12/17/09 9:18:09 PM CONTENTS.0110 VOLUME 17 NUMBER 1 POSTMORTEM DEPARTMENTS 20 NCSOFT'S AION 2 GAME PLAN By Brandon Sheffield [EDITORIAL] AION is NCsoft's next big subscription MMORPG, originating from Going Through the Motions the company's home base in South Korea. In our first-ever Korean postmortem, the team discusses how AION survived worker 4 HEADS UP DISPLAY [NEWS] fatigue, stock drops, and real money traders, providing budget and Open Source Space Games, new NES music engine, and demographics information along the way. Gamma IV contest announcement. By NCsoft South Korean team 34 TOOL BOX By Chris DeLeon [REVIEW] FEATURES Unity Technologies' Unity 2.6 7 2009 FRONT LINE AWARDS 38 THE INNER PRODUCT By Jake Cannell [PROGRAMMING] We're happy to present our 12th annual tools awards, representing Brick by Brick the best in game industry software, across engines, middleware, production tools, audio tools, and beyond, as voted by the Game 42 PIXEL PUSHER By Steve Theodore [ART] Developer audience. Tilin'? Stylin'! By Eric Arnold, Alex Bethke, Rachel Cordone, Sjoerd De Jong, Richard Jacques, Rodrigue Pralier, and Brian Thomas. 46 DESIGN OF THE TIMES By Damion Schubert [DESIGN] Get Real 15 RETHINKING USER INTERFACE Thinking of making a game for multitouch-based platforms? This 48 AURAL FIXATION By Jesse Harlin [SOUND] article offers a look at the UI considerations when moving to this sort of Dethroned interface, including specific advice for touch offset, and more. By Brian Robbins 50 GOOD JOB! [CAREER] Konami sound team mass exodus, Kim Swift interview, 27 CENTER OF MASS and who went where.
    [Show full text]
  • Skyfire: Data-Driven Seed Generation for Fuzzing
    Skyfire: Data-Driven Seed Generation for Fuzzing Junjie Wang, Bihuan Chen†, Lei Wei, and Yang Liu Nanyang Technological University, Singapore {wang1043, bhchen, l.wei, yangliu}@ntu.edu.sg †Corresponding Author Abstract—Programs that take highly-structured files as inputs Syntax Semantic normally process inputs in stages: syntax parsing, semantic check- Features Rules ing, and application execution. Deep bugs are often hidden in the <?xml version="1.0" application execution stage, and it is non-trivial to automatically encoding="utf- pass pass pass 8"?><xsl:stylesheet version="1.0" Syntax Semantic Application xmlns:xsl="http://www.w3 .org/1999/XSL/Transform" generate test inputs to trigger them. Mutation-based fuzzing gen- ><xsl:output xsl:use- √ attribute- Parsing Checking Execution erates test inputs by modifying well-formed seed inputs randomly sets=""/></xsl:stylesheet> Parsing Semantic or heuristically. Most inputs are rejected at the early syntax pars- Inputs Crashes ing stage. Differently, generation-based fuzzing generates inputs Errors Violations from a specification (e.g., grammar). They can quickly carry the ! ! X fuzzing beyond the syntax parsing stage. However, most inputs fail to pass the semantic checking (e.g., violating semantic rules), Fig. 1: Stages of Processing Highly-Structured Inputs which restricts their capability of discovering deep bugs. In this paper, we propose a novel data-driven seed generation approach, named Skyfire, which leverages the knowledge in the analysis [8, 9] that identifies those interesting bytes to mutate, vast amount of existing samples to generate well-distributed seed symbolic execution [10, 11, 12] that relies on constraint solving inputs for fuzzing programs that process highly-structured inputs.
    [Show full text]
  • Cisco ACE XML Gateway Installation and Administration Guide Software Version 5.1
    Cisco ACE XML Gateway Installation and Administration Guide Software Version 5.1 Cisco Systems, Inc. | 170 West Tasman Drive | San Jose, CA 95134-1706 | 800 553-6387 THE SPECIFICATIONS AND INFORMATION REGARDING THE PRODUCTS IN THIS MANUAL ARE SUBJECT TO CHANGE WITHOUT NOTICE. ALL STATEMENTS, INFORMATION, AND RECOMMENDATIONS IN THIS MANUAL ARE BELIEVED TO BE ACCURATE BUT ARE PRESENTED WITHOUT WARRANTY OF ANY KIND, EXPRESS OR IMPLIED. USERS MUST TAKE FULL RESPONSIBILITY FOR THEIR APPLICATION OF ANY PRODUCTS. THE SOFTWARE LICENSE AND LIMITED WARRANTY FOR THE ACCOMPANYING PRODUCT ARE SET FORTH IN THE INFORMATION PACKET THAT SHIPPED WITH THE PRODUCT AND ARE INCORPORATED HEREIN BY THIS REFERENCE. IF YOU ARE UNABLE TO LOCATE THE SOFTWARE LICENSE OR LIMITED WARRANTY, CONTACT YOUR CISCO REPRESENTATIVE FOR A COPY. NOTWITHSTANDING ANY OTHER WARRANTY HEREIN, ALL DOCUMENT FILES AND SOFTWARE OF THESE SUPPLIERS ARE PROVIDED “AS IS” WITH ALL FAULTS. CISCO AND THE ABOVE-NAMED SUPPLIERS DISCLAIM ALL WARRANTIES, EXPRESSED OR IMPLIED, INCLUDING, WITHOUT LIMITATION, THOSE OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT OR ARISING FROM A COURSE OF DEALING, USAGE, OR TRADE PRACTICE.IN NO EVENT SHALL CISCO OR ITS SUPPLIERS BE LIABLE FOR ANY INDIRECT, SPECIAL, CONSEQUENTIAL, OR INCIDENTAL DAMAGES, INCLUDING, WITHOUT LIMITATION, LOST PROFITS OR LOSS OR DAMAGE TO DATA ARISING OUT OF THE USE OR INABILITY TO USE THIS MANUAL, EVEN IF CISCO OR ITS SUPPLIERS HAVE BEEN ADVISED OF THE POSSIBILITY OF SUCH DAMAGES. CCVP, the Cisco Logo, and the
    [Show full text]
  • Solaris Express Developer Edition
    Новые функции и возможности в Solaris Express Developer Edition Beta Sun Microsystems, Inc. 4150 Network Circle Santa Clara, CA 95054 U.S.A. Номер по каталогу: 820–2601–03 Январь 2008 © 2008 Sun Microsystems, Inc. 4150 Network Circle, Santa Clara, CA 95054 U.S.A. Все права защищены. Sun Microsystems, Inc. обладает правами на интеллектуальную собственность в отношении технологий, реализованных в рассматриваемом в настоящем документе продукте. В частности и без ограничений, эти права на интеллектуальную собственность могут включать в себя один или более патентов США или заявок на патент в США и в других странах. Права Правительства США – Коммерческое программное обеспечение. К правительственным пользователям относится стандартное лицензионное соглашение Sun Microsystems, Inc, а также применимые положения FAR с приложениями. В этот продукт могут входить материалы, разработанные третьими сторонами. Отдельные части продукта могут быть заимствованы из систем Berkeley BSD, предоставляемых по лицензии университета штата Калифорния. UNIX является товарным знаком, зарегистрированным в США и других странах, и предоставляется по лицензии исключительно компанией X/Open Company, Ltd. Sun, Sun Microsystems, логотип Sun, логотип Solaris, логотип Java Coffee Cup, docs.sun.com, Java и Solaris являются товарными знаками или зарегистрированными товарными знаками Sun Microsystems, Inc. в США и других странах. Все товарные знаки SPARC используются по лицензии и являются товарными знаками или зарегистрированными товарными знаками SPARC International, Inc. в США и других странах. Продукты, носящие торговые знаки SPARC, основаны на архитектуре, разработанной Sun Microsystems, Inc. Adobe – зарегистрированный товарный знак Adobe Systems, Incorporated. Графический интерфейс пользователя OPEN LOOK и SunTM был разработан компанией Sun Microsystems, Inc. для ее пользователей и лицензиатов. Компания Sun признает, что компания Xerox первой начала исследования и разработку концепции визуального или графического интерфейсов пользователя для компьютерной индустрии.
    [Show full text]
  • Using XSL and Mod Transform in Apache Applications
    Using XSL and mod_transform in Apache Applications Paul Querna [email protected] What is XSL? ● Extensible Stylesheet Language (XSL) ● A family of Standards for XML by the W3C: – XSL Transformations (XSLT) – XML Path Language (Xpath) – XSL Formatting Objects (XSL-FO) XSLT Example <?xml version="1.0"?> <xsl:stylesheet xmlns:xsl="http://www.w3.org/1999/XSL/Transform" version="1.0"> <xsl:template match="/"> <html> <head><title>A Message</title></head> <body> <h1> <xsl:value-of select="message" /> </h1> </body> </html> </xsl:template> </xsl:stylesheet> Data Source... <?xml version="1.0"?> <message>Hello World</message> Outputs... <html> <head> <meta http-equiv="Content-Type" content="text/html; charset=UTF-8"> <title>A Message</title> </head> <body> <h1>Hello World</h1> </body> </html> Why is XSLT good? ● Mixing Data and Presentation is bad! – Keeps Data in a clean XML schema – Keeps the Presentation of this Data separate ● XSLT is XML ● Easy to Extend ● Put HTML or other Markups directly in the XSLT. – Easy for Web Developers to create a template Why is XSLT bad? ● XSLT is XML ● Complicated XSLT can be slow ● Yet another language to learn Where does Apache fit in this? ● Apache 2.0 has Filters! Input Handlers Client Filters (Perl, PHP, Proxy, File) Output Filters mod_include (SSI) mod_transform (XSLT) mod_deflate (gzip) mod_transform ● Uses libXML2 and libXSLT from Gnome – C API ● Doesn't depend on other Gnome Libs. – Provides: ● EXSLT ● XInclude ● XPath ● Xpointer ● ... and more Static XML Files ● AddOutputFilter XSLT .xml ● TransformSet /xsl/foo.xsl – Only if your XML does not specify a XSL File ● TransformOptions +ApacheFS – Uses Sub-Requests to find files – Makes mod_transform work like Apache AxKit Dynamic Sources ● XML Content Types: – AddOutputFilterByType XSLT application/xml ● Controlled Content Types: – AddOutputFilterByType XSLT applicain/needs- xslt ● Works for Proxied Content, PHP, mod_perl, mod_python, CGI, SSI, etc.
    [Show full text]
  • Comparison of Indexers
    Comparison of indexers Beagle, JIndex, metaTracker, Strigi Michal Pryc, Xusheng Hou Sun Microsystems Ltd., Ireland November, 2006 Updated: December, 2006 Table of Contents 1. Introduction.............................................................................................................................................3 2. Indexers...................................................................................................................................................4 3. Test environment ....................................................................................................................................5 3.1 Machine............................................................................................................................................5 3.2 CPU..................................................................................................................................................5 3.3 RAM.................................................................................................................................................5 3.4 Disk..................................................................................................................................................5 3.5 Kernel...............................................................................................................................................5 3.6 GCC..................................................................................................................................................5
    [Show full text]
  • Pipenightdreams Osgcal-Doc Mumudvb Mpg123-Alsa Tbb
    pipenightdreams osgcal-doc mumudvb mpg123-alsa tbb-examples libgammu4-dbg gcc-4.1-doc snort-rules-default davical cutmp3 libevolution5.0-cil aspell-am python-gobject-doc openoffice.org-l10n-mn libc6-xen xserver-xorg trophy-data t38modem pioneers-console libnb-platform10-java libgtkglext1-ruby libboost-wave1.39-dev drgenius bfbtester libchromexvmcpro1 isdnutils-xtools ubuntuone-client openoffice.org2-math openoffice.org-l10n-lt lsb-cxx-ia32 kdeartwork-emoticons-kde4 wmpuzzle trafshow python-plplot lx-gdb link-monitor-applet libscm-dev liblog-agent-logger-perl libccrtp-doc libclass-throwable-perl kde-i18n-csb jack-jconv hamradio-menus coinor-libvol-doc msx-emulator bitbake nabi language-pack-gnome-zh libpaperg popularity-contest xracer-tools xfont-nexus opendrim-lmp-baseserver libvorbisfile-ruby liblinebreak-doc libgfcui-2.0-0c2a-dbg libblacs-mpi-dev dict-freedict-spa-eng blender-ogrexml aspell-da x11-apps openoffice.org-l10n-lv openoffice.org-l10n-nl pnmtopng libodbcinstq1 libhsqldb-java-doc libmono-addins-gui0.2-cil sg3-utils linux-backports-modules-alsa-2.6.31-19-generic yorick-yeti-gsl python-pymssql plasma-widget-cpuload mcpp gpsim-lcd cl-csv libhtml-clean-perl asterisk-dbg apt-dater-dbg libgnome-mag1-dev language-pack-gnome-yo python-crypto svn-autoreleasedeb sugar-terminal-activity mii-diag maria-doc libplexus-component-api-java-doc libhugs-hgl-bundled libchipcard-libgwenhywfar47-plugins libghc6-random-dev freefem3d ezmlm cakephp-scripts aspell-ar ara-byte not+sparc openoffice.org-l10n-nn linux-backports-modules-karmic-generic-pae
    [Show full text]