Language Selection

English French German Italian Portuguese Spanish

The secret plan behind the “3.0 (quilt)” Debian source package format

Filed under
Software

While I have spent countless hours working on the new source format known as “3.0 (quilt)”, I’ve just realized that I have never blogged about its features and the reasons that lead me to work on it. Let’s fix this.

Design goals for the new formats

When I started working on the new source package format, I set out to get rid of all the known limitations and to integrate a patch system in dpkg-source. I wanted to clear up the situation so that learning packaging only requires to learn one patch system and would not require modifying debian/rules to use it. I picked quilt because it was popular, came with a large set of features, and was not suffering from NIH syndrome. This lead to the “3.0 (quilt)” source format.

I also created “3.0 (native)” as a distinct format. “1.0″ was able to generate two types of source packages (native and non-native) but I did not want to continue with this mistake of mixing both in a single format. The KISS principle dictated that the user should pick the format of his choice, put it in debian/source/format and be done with it. Now the build can rightfully fail when the requirements are not met instead of doing something unexpected as a fallback.

Features of “3.0 (quilt)”




More in Tux Machines

Debian GNU/Linux 9 "Stretch" to Ship with GCC 6 by Default, Binutils 2.27

Debian developer Matthias Klose has announced that the new GCC 6 compiler, which will be made the default GCC compiler for the upcoming Debian GNU/Linux 9 "Stretch" operating system, is now available in the Debian Testing repos. Debian users who are currently using Debian Testing can make GCC 6 the default compiler by installing the gcc/g++ packages from experimental. If installing it, they are also urged to help fix reported built failures in Debian Testing and Debian Unstable. Read more

Canonical Demonstrates How Easy It Is to Create a Vendor-Independent Snap Store

The Snappy vs. Flatpak story continues, and Canonical is now demonstrating how easy it is to roll out a vendor-independent Snap store on the recently released Fedora 24 Linux operating system. A couple of days ago, Canonical and Ubuntu founder Mark Shuttleworth finally answered one of the big questions many members of the GNU/Linux community had been asking since the unveiling of Snaps as universal binary formats for major Linux kernel-based operating systems. Read more

Fedora: Latest News

  • EMEA Sponsorship Program for Flock 2016
    In the past we have had a tradition of sponsoring EMEA contributors that would like to attend Flock but are not going to receive funding as speakers.
  • New badge: Red Hat Summit 2016 !
  • New FMN architecture and tests
    FMN is the FedMsg Notification service. It allows any contributors (or actually, anyone with a FAS account) to tune what notification they want to receive and how.
  • GSoC 2016 Weekly Rundown: Assembling the orchestra
    This week is the Google Summer of Code 2016 midterm evaluation week. Over the past month since the program started, I’ve learned more about the technology I’m working with, implementing it within my infrastructure, and moving closer to completing my proposal. My original project proposal details how I am working with Ansible to bring improved automation for WordPress platforms within Fedora, particularly to the Fedora Community Blog and the Fedora Magazine.
  • Fedora 24, SourceForge’s Dilemma & More…
    It’s baseball season, and in baseball about this time of year talk turns to trades. Well, I’ve been traded for one game…er, review. That means that although I’ve downloaded and installed Fedora 24 on our test machine, I can’t really give it a full review here. However, I’ll make sure to point you to the review as soon as it goes up “on another network,” as Johnny Carson used to say. All I can tell you now is that so far it seems to do what it does well.

Android Leftovers