DOCSLIB.ORG

How to Collaborate on Linux Kernel Development

Total Page：16

File Type：pdf, Size：1020Kb

Download full-text PDF Read full-text
How to Collaborate on Linux Kernel Development How to Collaborate on Linux Kernel Development Mauro Carvalho Chehab Linux Kernel Expert Samsung Research Brazil Samsung Open Source Group Oct 17, 2014 Not to be used for commercial purpose without getting permission Open Source Group – Silicon Valley All information, opinions and ideas herein are exclusively the author's own opinion © 2014 SAMSUNG Electronics Co. Samsung Research Brazil Contributing to the Linux Kernel Copyright 2 Open Source Group – Silicon Valley © 2014 SAMSUNG Electronics Co. Samsung Research Brazil Copyright ● Authors have rights on the contents they produce: – Moral rights: the rights to claim its authorship on a work and to be against modified copies that would cause moral harm to the author; – Property rights: the ones that could generate profits (sell, distribute, publish, rent, copy, use). – Applies to intellectual work, like books, paintings, music, software ● Public domain – Something that was not copyrighted – No restrictions are imposed to its usage: anyone can copy, modify, use, etc 3 Open Source Group – Silicon Valley © 2014 SAMSUNG Electronics Co. Samsung Research Brazil Copyright x Public Domain ● A Copyright traditional model that doesn't help collaboration, as the holder of a copyright is typically the only one that benefits for its work. ● On the other hand, putting some work in public domain makes collaboration possible, but it would mean to loose all rights on such work. ● So, the Open Source movement came with a new concept, called Copyleft, where the author keep holding the rights on his work, while creating a hole community of developers helping to improve and to create new ways of using his work. The real gain with Open Source is to build an eco system that will keep the products well maintained, well supported and allowing new ways of usage. It is a trully win to win model. 4 Open Source Group – Silicon Valley © 2014 SAMSUNG Electronics Co. Samsung Research Brazil Copyleft ● It is a variant of the Copyright: the rights belong to the authors ● The author gives the right (via a software license) that allows copy, distribute, modify and usage ● Modified copies should also be licensed under the same copyleft license ● A violation to a copyleft license is a copyright violation Open Source Group – Silicon Valley © 2014 SAMSUNG Electronics Co. Samsung Research Brazil Contributing to the Linux Kernel Licensing 6 Open Source Group – Silicon Valley © 2014 SAMSUNG Electronics Co. Samsung Research Brazil GPL - version 2 (1) http://www.gnu.org/licenses/gpl-2.0.html ● The GNU General Public License is intended to guarantee your freedom to share and change free software – to make sure the software is free for all its users – Free software: freedom (not price) ● Freedom to distribute copies of free software – and charge for this service if you wish ● Receive source code or can get it if you want it ● Can change the software or use pieces of it in new free programs ● Rights remain the same after copied/modified: – If copies are distributed (whether gratis or for a fee): the recipients has all the rights that the distributor have; – The same license applies to distributed copies; 7 Open Source Group – Silicon Valley © 2014 SAMSUNG Electronics Co. Samsung Research Brazil GPL - version 2 (2) http://www.gnu.org/licenses/gpl-2.0.html ● Rights protected by GPLv2: – Software is copyrighted; – It gives legal permission to copy, distribute and/or modify the software. – Moral rights protection: ● If the software is modified by someone else and passed on, we want its recipients to know that what they have is not the original, so that any problems introduced by others will not reflect on the original authors' reputations. – Patents: there are clauses stating that any patent must be licensed for everyone's free use or not licensed at all. 8 Open Source Group – Silicon Valley © 2014 SAMSUNG Electronics Co. Samsung Research Brazil GPL License used on Kernel ● Kernel is licensed under GPL version 2 only ● There's an extra clause at Kernel that explicitly allows running userspace using other licenses: NOTE! This copyright does *not* cover user programs that use kernel services by normal system calls - this is merely considered normal use of the kernel, and does *not* fall under the heading of "derived work". Also note that the GPL below is copyrighted by the Free Software Foundation, but the instance of code that it refers to (the Linux kernel) is copyrighted by me and others who actually wrote it. 9 Open Source Group – Silicon Valley © 2014 SAMSUNG Electronics Co. Samsung Research Brazil Contributing to the Linux Kernel Interacting with an upstream development Community Open Source Group – Silicon Valley © 2014 SAMSUNG Electronics Co. Samsung Research Brazil Netettiquete: email ● Most of the Open Source discussions happen via email; ● RTFM: Read The F#$& Fine Manual – Before sending something to a public ML, you should check first if your questions/patches/etc weren't already sent to it; ● Be polite; ● Be prepared for critics: – That's part of the game; ● Don't be offended by emails; ● Don't feed the Mailing List trolls. Open Source Group – Silicon Valley © 2014 SAMSUNG Electronics Co. Samsung Research Brazil Warning: Don't mangle emails ● There are several important rules when sending emails to a public ML: – Always send emails in plain text: ● There are security issues on using html – most lists block it; – Never do top-posting: answers should be below questions ● Just the opposite way that Outlook does – Use an email client that won't mangle whitespaces ● Whitespace insert/removal would break patches ● Best option nowadays: use git send-email Open Source Group – Silicon Valley © 2014 SAMSUNG Electronics Co. Samsung Research Brazil The Development Model (1) ● Upstream development is dictated by the community, not by someone or some company – If someone (and/or their company) wants a feature, submit a patch ● The community reviews the patch; ● If community is happy, it gets merged, otherwise, it is rejected ● The development communities are huge, informal and open – All discussions are via mailing lists ● On Kernel, most lists are hosted at vger.kernel.org; – IRC and physical meetings (Summits and/or BoF – Birds of Feather) help to get agreements on more polemic items ● BoFs are informal and often formed in an ad hoc manner. ● IRC channels are generally hosted at freenode.net (or oftc.net) – Examples at Freenode: #tizen, #v4l, #linuxtv, #gstreamer 13 Open Source Group – Silicon Valley © 2014 SAMSUNG Electronics Co. Samsung Research Brazil The Development Model (2) ● Contributions are open to everyone, and patches are publicly reviewed – Reviewing a patch internally inside a company is generally considered a bad habit, as the community won't give a single penny for such reviews made under black walls; ● On most packages, the version number indicates if the version is a review or a major change with API breakages, as specified at http://semver.org : – Given a version number MAJOR.MINOR.PATCH, increment the: ● MAJOR version when you make incompatible API changes, ● MINOR version when you add functionality in a backwards- compatible manner, ● PATCH version when you make backwards-compatible bug fixes. – NOTE: Not all projects follow it, including the Linux Kernel! Open Source Group – Silicon Valley © 2014 SAMSUNG Electronics Co. Samsung Research Brazil Contributing to the Linux Kernel Interacting with the Kernel community Open Source Group – Silicon Valley © 2014 SAMSUNG Electronics Co. Samsung Research Brazil The Kernel Development Model (1) ● The Linux Kernel version number is, currently: – 3.x – For released Kernels; – 3.x.y – For stable fixes for a released Kernel; – 3.x-rcy – For Release Candidate Kernels (one per week); ● A new Linux Kernel version is released on every ~2 months – After a new release, 2 weeks are used to merge the features for the next one. This period of time is called: “merge window”; – A variable period (typically 6-8 weeks) is used to review the code. After each week, a new release candidate is released ● So, there are 3.16-rc1 to 3.16-rc7, plus 3.16 (the final version). ● Subsystem maintainers are responsible to collect the accepted patches, do a final review and submit them to Linus Torvards (the creator of Linux) and main maintainer. Open Source Group – Silicon Valley © 2014 SAMSUNG Electronics Co. Samsung Research Brazil The Kernel Development Model (2) 17 Open Source Group – Silicon Valley © 2014 SAMSUNG Electronics Co. Samsung Research Brazil Interacting with the community Maintainers are like editors in the Publishing industry. - David Miller Linux Kernel Networking Maintainer TIP: please listen Greg K. H. presentation: I don't want your code: http://www.cnx-software.com/2013/03/07/linaro-connect-hk-greg-kroah-hartman-keynote-i-dont-want-your-code/ Open Source Group – Silicon Valley © 2014 SAMSUNG Electronics Co. Samsung Research Brazil Do I need a tough skin to be a kernel devel? ● The Linux kernel community is very technically brutal when it comes to code review. – a particular format that need the patches to fit, and newbies often get it wrong; – You should look at the patch format of several different commits in the git history; – Very high standard for coding style and the patch submission process. ● Subsystem maintainers can also be particularly picky when patches come in from a newbie – Since they've never seen code from you before, they don't know what the newbie's skill level; – Often, new contributors are held to higher standards than the long- term ones. (cont.) http://kernelnewbies.org/KernelDevViewpoint
Load more

Recommended publications
  • Debian Developer's Reference Version 12.0, Released on 2021-09-01
    Debian Developer’s Reference Release 12.0 Developer’s Reference Team 2021-09-01 CONTENTS 1 Scope of This Document 3 2 Applying to Become a Member5 2.1 Getting started..............................................5 2.2 Debian mentors and sponsors......................................6 2.3 Registering as a Debian member.....................................6 3 Debian Developer's Duties 9 3.1 Package Maintainer's Duties.......................................9 3.1.1 Work towards the next stable release............................9 3.1.2 Maintain packages in stable .................................9 3.1.3 Manage release-critical bugs.................................. 10 3.1.4 Coordination with upstream developers............................ 10 3.2 Administrative Duties.......................................... 10 3.2.1 Maintaining your Debian information............................. 11 3.2.2 Maintaining your public key.................................. 11 3.2.3 Voting.............................................. 11 3.2.4 Going on vacation gracefully.................................. 12 3.2.5 Retiring............................................. 12 3.2.6 Returning after retirement................................... 13 4 Resources for Debian Members 15 4.1 Mailing lists............................................... 15 4.1.1 Basic rules for use....................................... 15 4.1.2 Core development mailing lists................................. 15 4.1.3 Special lists........................................... 16 4.1.4 Requesting new
    [Show full text]
  • Beginning Portable Shell Scripting from Novice to Professional
    Beginning Portable Shell Scripting From Novice to Professional Peter Seebach 10436fmfinal 1 10/23/08 10:40:24 PM Beginning Portable Shell Scripting: From Novice to Professional Copyright © 2008 by Peter Seebach All rights reserved. No part of this work may be reproduced or transmitted in any form or by any means, electronic or mechanical, including photocopying, recording, or by any information storage or retrieval system, without the prior written permission of the copyright owner and the publisher. ISBN-13 (pbk): 978-1-4302-1043-6 ISBN-10 (pbk): 1-4302-1043-5 ISBN-13 (electronic): 978-1-4302-1044-3 ISBN-10 (electronic): 1-4302-1044-3 Printed and bound in the United States of America 9 8 7 6 5 4 3 2 1 Trademarked names may appear in this book. Rather than use a trademark symbol with every occurrence of a trademarked name, we use the names only in an editorial fashion and to the benefit of the trademark owner, with no intention of infringement of the trademark. Lead Editor: Frank Pohlmann Technical Reviewer: Gary V. Vaughan Editorial Board: Clay Andres, Steve Anglin, Ewan Buckingham, Tony Campbell, Gary Cornell, Jonathan Gennick, Michelle Lowman, Matthew Moodie, Jeffrey Pepper, Frank Pohlmann, Ben Renow-Clarke, Dominic Shakeshaft, Matt Wade, Tom Welsh Project Manager: Richard Dal Porto Copy Editor: Kim Benbow Associate Production Director: Kari Brooks-Copony Production Editor: Katie Stence Compositor: Linda Weidemann, Wolf Creek Press Proofreader: Dan Shaw Indexer: Broccoli Information Management Cover Designer: Kurt Krames Manufacturing Director: Tom Debolski Distributed to the book trade worldwide by Springer-Verlag New York, Inc., 233 Spring Street, 6th Floor, New York, NY 10013.
    [Show full text]
  • Leitfaden Für Debian-Betreuer
    Leitfaden für Debian­Betreuer Osamu Aoki, Helge Kreutzmann, and Mechtilde Stehmann August 27, 2021 Leitfaden für Debian­Betreuer by Osamu Aoki, Helge Kreutzmann, and Mechtilde Stehmann Copyright © 2014­2020 Osamu Aoki Permission is hereby granted, free of charge, to any person obtaining a copy of this software and associated documentation files (the ”Software”), to deal in the Software without restriction, including without limitation the rights to use, copy, modify, merge, publish, distribute, sublicense, and/or sell copies of the Software, and to permit persons to whom the Software is furnished to do so, subject to the following conditions: The above copyright notice and this permission notice shall be included in all copies or substantial portions of the Software. THE SOFTWARE IS PROVIDED ”AS IS”, WITHOUT WARRANTY OF ANY KIND, EXPRESS OR IM­ PLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE. Diese Anleitung wurde mit den nachfolgenden Dokumenten als Referenz erstellt: • »Making a Debian Package (AKA the Debmake Manual)«, Copyright © 1997 Jaldhar Vyas. • »The New­Maintainer’s Debian Packaging Howto«, Copyright © 1997 Will Lowe. • »Debian­Leitfaden für Neue Paketbetreuer«, Copyright © 1998­2002 Josip Rodin, 2005­2017 Osamu Aoki, 2010 Craig Small und 2010 Raphaël Hertzog. Die neuste Version dieser Anleitung sollte • im Paket debmake­doc und • auf der Debian­Dokumentations­Website verfügbar sein.
    [Show full text]
  • Compiling C Programs
    CSCI 2132: Software Development Lab 6: Exploring bash and C Compilation Synopsis In this lab, you will: • Customize the behaviour your bash shell • Write and compile some simple C programs • Practice the edit-compile-fix cycle using emacs and the shell • Learn to patch programs using diff and patch Contents Overview......................................................................................................2 Step 1: Login and lab setup.................................................................................3 Step 2: The name of your shell.............................................................................3 Step 3: The .bashrc file.....................................................................................3 Step 4: Customize rm ........................................................................................4 Optional Step: Install bashrc.new as your new .bashrc file............................................7 Step 5: Edit .profile .......................................................................................8 Optional Step: Install profile.new as your new .profile file.......................................... 10 Step 6: Write a simple C program.......................................................................... 11 Step 7: Explore exit codes................................................................................... 12 Step 8: diff .................................................................................................. 14 Step 9: patch................................................................................................
    [Show full text]
  • Distributed Revision Control with Mercurial
    Distributed revision control with Mercurial Bryan O’Sullivan Copyright c 2006, 2007 Bryan O’Sullivan. This material may be distributed only subject to the terms and conditions set forth in version 1.0 of the Open Publication License. Please refer to Appendix D for the license text. This book was prepared from rev 028543f67bea, dated 2008-08-20 15:27 -0700, using rev a58a611c320f of Mercurial. Contents Contents i Preface 2 0.1 This book is a work in progress ...................................... 2 0.2 About the examples in this book ..................................... 2 0.3 Colophon—this book is Free ....................................... 2 1 Introduction 3 1.1 About revision control .......................................... 3 1.1.1 Why use revision control? .................................... 3 1.1.2 The many names of revision control ............................... 4 1.2 A short history of revision control .................................... 4 1.3 Trends in revision control ......................................... 5 1.4 A few of the advantages of distributed revision control ......................... 5 1.4.1 Advantages for open source projects ............................... 6 1.4.2 Advantages for commercial projects ............................... 6 1.5 Why choose Mercurial? .......................................... 7 1.6 Mercurial compared with other tools ................................... 7 1.6.1 Subversion ............................................ 7 1.6.2 Git ................................................ 8 1.6.3
    [Show full text]
  • Debianization of Predictprotein
    debian-unstable package-building git-repository lintian and quilt sources Programming challenge 10: Debianization of PredictProtein Jens Preußner Supervisor: Laszlo Kajan The Bioinformatics Lab 10th of July, 2012 debian-unstable package-building git-repository lintian and quilt sources Table of contents 1 debian-unstable Installation 2 package-building Structure of directory Building 3 git-repository Local git repository Remote git repository Initial push 4 lintian and quilt Fixing lintian warnings Working with quilt 5 References Now perform as root: $ chroot /srv/unstable/ $ adduser --home /home/<user> --uid <uid> <user> $ su - <user> debian-unstable package-building git-repository lintian and quilt sources Installing debian-unstable in L1 Required packages: debootstrap, dpkg-dev - easy Bind your home and proc, see Network filesystems debian-unstable package-building git-repository lintian and quilt sources Installing debian-unstable in L1 Required packages: debootstrap, dpkg-dev - easy Bind your home and proc, see Network filesystems Now perform as root: $ chroot /srv/unstable/ $ adduser --home /home/<user> --uid <uid> <user> $ su - <user> debian-unstable package-building git-repository lintian and quilt sources Installing debian-unstable in L1 To know for sure, that you are in wheezy/sid In new environment: $ cat /etc/debian version wheezy/sid instead of 6.0.4 debian-unstable package-building git-repository lintian and quilt sources My special case I had a perl module for uploading The module was not contained in CPAN Naming conventions:
    [Show full text]
  • C/C++ Compile Guide
    WizFi630S Guide C/C++ Compile Guide (Version 1.0.0) © 2019 WIZnet Co., Ltd. All Rights Reserved. For more information, please visit our website at http://www.wiznet.io/ © Copyright 2019 WIZnet Co., Ltd. All rights reserved. 1 WizFi630S Guide Document Revision History Date Revision Changes 2019-11-25 1.0 Release © Copyright 2019 WIZnet Co., Ltd. All rights reserved. 2 WizFi630S Guide Contents 1. Overview ................................................................................................................. 4 2. Download ................................................................................................................ 4 2.1 Prerequisites .................................................................................................. 4 2.2 Packages for Building Environment .......................................................... 4 2.3 OpenWRT Firmware Repository................................................................. 6 2.4 Menuconfig .................................................................................................... 7 3. Write C Code........................................................................................................... 7 3.1 Helloworld ...................................................................................................... 7 3.2 Make the Environment Script .................................................................... 8 4. Cross Compile ......................................................................................................... 8 4.1
    [Show full text]
  • Buildroot Training Buildroot Training
    Buildroot Training Buildroot Training © Copyright 2004-2021, Bootlin. Creative Commons BY-SA 3.0 license. Latest update: October 6, 2021. Document updates and sources: https://bootlin.com/doc/training/buildroot Corrections, suggestions, contributions and translations are welcome! embedded Linux and kernel engineering Send them to [email protected] - Kernel, drivers and embedded Linux - Development, consulting, training and support - https://bootlin.com 1/353 Rights to copy © Copyright 2004-2021, Bootlin License: Creative Commons Attribution - Share Alike 3.0 https://creativecommons.org/licenses/by-sa/3.0/legalcode You are free: I to copy, distribute, display, and perform the work I to make derivative works I to make commercial use of the work Under the following conditions: I Attribution. You must give the original author credit. I Share Alike. If you alter, transform, or build upon this work, you may distribute the resulting work only under a license identical to this one. I For any reuse or distribution, you must make clear to others the license terms of this work. I Any of these conditions can be waived if you get permission from the copyright holder. Your fair use and other rights are in no way affected by the above. Document sources: https://github.com/bootlin/training-materials/ - Kernel, drivers and embedded Linux - Development, consulting, training and support - https://bootlin.com 2/353 Hyperlinks in the document There are many hyperlinks in the document I Regular hyperlinks: https://kernel.org/ I Kernel documentation links: dev-tools/kasan I Links to kernel source files and directories: drivers/input/ include/linux/fb.h I Links to the declarations, definitions and instances of kernel symbols (functions, types, data, structures): platform_get_irq() GFP_KERNEL struct file_operations - Kernel, drivers and embedded Linux - Development, consulting, training and support - https://bootlin.com 3/353 Company at a glance I Engineering company created in 2004, named ”Free Electrons” until Feb.
    [Show full text]
  • Debian Packaging Tutorial
    Debian Packaging Tutorial Lucas Nussbaum [email protected] version 0.27 – 2021-01-08 Debian Packaging Tutorial 1 / 89 About this tutorial I Goal: tell you what you really need to know about Debian packaging I Modify existing packages I Create your own packages I Interact with the Debian community I Become a Debian power-user I Covers the most important points, but is not complete I You will need to read more documentation I Most of the content also applies to Debian derivative distributions I That includes Ubuntu Debian Packaging Tutorial 2 / 89 Outline 1 Introduction 2 Creating source packages 3 Building and testing packages 4 Practical session 1: modifying the grep package 5 Advanced packaging topics 6 Maintaining packages in Debian 7 Conclusions 8 Additional practical sessions 9 Answers to practical sessions Debian Packaging Tutorial 3 / 89 Outline 1 Introduction 2 Creating source packages 3 Building and testing packages 4 Practical session 1: modifying the grep package 5 Advanced packaging topics 6 Maintaining packages in Debian 7 Conclusions 8 Additional practical sessions 9 Answers to practical sessions Debian Packaging Tutorial 4 / 89 Debian I GNU/Linux distribution I 1st major distro developed “openly in the spirit of GNU” I Non-commercial, built collaboratively by over 1,000 volunteers I 3 main features: I Quality – culture of technical excellence We release when it’s ready I Freedom – devs and users bound by the Social Contract Promoting the culture of Free Software since 1993 I Independence – no (single)
    [Show full text]
  • Debian Packaging with Git WorkOws and Tools
    Debian Packaging with Git Workows and Tools David Bremner 26 July 2011 Introduction Importing Upstream Source Importing Repacking ./debian Handling patches Simplest approaches Use git for patches Rebased patch branches making a source package (in)Conclusions Advanced Topics/Brainstorming Goals for the talk I take away some of the mystery I know what is possible I have some discussion about best practices Talk pre-reqs and goals Talk-Depends: basic-packaging (>=1.0), git-curious I You know what a source package is I You know what a git branch and tag is (or want to) Talk pre-reqs and goals Talk-Depends: basic-packaging (>=1.0), git-curious I You know what a source package is I You know what a git branch and tag is (or want to) Goals for the talk I take away some of the mystery I know what is possible I have some discussion about best practices The Packaging Cycle 1. start with upstream source 2. possibly remove some non-free or just useless things 3. create or update ./debian 4. possibly patch upstream source 5. make a source package Introduction Importing Upstream Source Importing Repacking ./debian Handling patches Simplest approaches Use git for patches Rebased patch branches making a source package (in)Conclusions Advanced Topics/Brainstorming Importing Upstream Source I at least one of import git import svn I get upstream $VCS history I unpack tarball I commit changes (including deletions) manual import I maybe save a copy using pristine-tar I maybe merge upstream in debian packaging branch I maybe tag pristine-tar I Allows checksum-identical regeneration of tarballs, small overhead pristine-tar commit foo.tar.gz [upstream-ref] pristine-tar checkout where-ever/foo.tar.gz I convenience feature, but for some rare tarballs, it doesn't work (well) Tracking upstream $VCS and tarballs I Get $VCS history on a branch I Import tarball on top: dis are contained in the import commit.
    [Show full text]
  • The Openwrt Embedded Development Framework
    The OpenWrt embedded development framework Florian Fainelli - fl[email protected] January 22, 2008 Abstract One of the biggest challenges to getting started with embedded devices is that you cannot just install a copy of Linux and expect to be able to compile a firmware. Even if you did remember to install a compiler and every development tool offered, you still would not have the basic set of tools needed to produce a firmware image. The embedded device represents an entirely new hardware platform, so in a process called cross compiling you need to produce a new compiler capable of generating code for your embedded platform, and then use it to compile a basic Linux distribution to run on your device. The process of creating a cross compiler can be tricky and in many cases when you are dealing with embedded devices you will be pro- vided with a binary copy of a compiler and basic libraries rather than instructions for creating your own. Likewise, it is also common to be provided with a patched copy of the Linux kernel from the board or chip vendor, but this is also dated and it can be difficult to spot ex- actly what has been modified to make the kernel run on the embedded platform. OpenWrt has different approach to building a firmware; down- loading, patching and compiling everything from scratch, including the cross compiler. OpenWrt does not contain any executables and only very few sources, it is an automated system for downloading the sources, patching them to work with the given platform and compil- ing them correctly for that platform.
    [Show full text]
  • Latest Features of Dpkg-Dev
    Latest features of dpkg-dev By Raphaël Hertzog <[email protected]> Mini-Debconf Paris 30-31 Oct 2010 Université Paris 7 What I'm going to cover ● New features of dpkg-dev in the last 2-3 years ● dpkg-dev: tools used to build debian packages ● In particular: ● Support of symbols files by dpkg-shlibdeps, dpkg-gensymbols ● Support of new source formats by dpkg-source ● Supplementary options for dpkg-source ● Cross distribution collaboration with dpkg-vendor ● Custom compilation flags with dpkg-buildflags ● Miscellaneous improvements to other tools Support of symbols files ● Before: shlibs files: library used → dependency with minimal version ● Now: symbols files: ● Library used → dependency template ● Symbol used → minimal version for dependency ● dpkg-shlibdeps can thus generate more accurate dependencies with relaxed requirements in many cases ● dpkg-gensymbols needed to generate the symbols files Example of shlibs/symbols files Shlibs file: libc 6 libc6 (>= 2.11) Symbols file: libc.so.6 libc6 #MINVER# | libc6 (>> 2.11), libc6 (<< 2.12) abs@GLIBC_2.0 2.0 accept4@GLIBC_2.10 2.10 duplocale@GLIBC_2.3 2.3 errno@GLIBC_PRIVATE 0 1 [...] More symbols goodness ● Ensuring generated dependency is as strong as the corresponding build-dependency ● Example: libgtk-x11-2.0.so.0 libgtk2.0-0 #MINVER# * Build-Depends-Package: libgtk2.0-dev gtk_about_dialog_get_artists@Base 2.8.0 [...] ● If a package build-depends on libgtk2.0-dev (>> 2.12), the dependency on libgtk2.0-0 will be at least as strict (i.e. >> 2.12). Adding symbols files in a source package
    [Show full text]