Difference between revisions of "Packaging"

From LSDevLinux
Jump to: navigation, search
(Initial creation)
 
(Further Reading: Add link to gbp guide)
 
(4 intermediate revisions by 2 users not shown)
Line 5: Line 5:
 
# Initial creation of the package
 
# Initial creation of the package
 
# Ongoing maintenance as a result of
 
# Ongoing maintenance as a result of
## Upstream upgrades
+
#* Upstream upgrades
## Distro upgrades
+
#* Distro upgrades
  
 
In this context, "upstream" refers to the original source of the software, before it is packaged. Usually this will be a developer's tarball or source-control repo.
 
In this context, "upstream" refers to the original source of the software, before it is packaged. Usually this will be a developer's tarball or source-control repo.
  
Once a package has been created, the control files that are used to describe and build the package can be re-used for the ongoing maintenance work with very little extra effort.
+
Once a package has been created, the control files that are used to describe and build the package can be re-used for the ongoing maintenance work with very little extra effort. Initial creation and ongoing maintenance may therefore be done by different people.
  
A tutorial for making packages for Debian-based systems (especially Ubuntu) is in [[Packaging using Pbuilder]].
+
== Further Reading ==
 +
 
 +
On this wiki:
 +
 
 +
* A [[Packaging using Pbuilder|tutorial]] for making packages for Debian-based systems (especially Ubuntu).
 +
* A [[Packaging using gbp|guide]] to using <code>[https://honk.sigxcpu.org/piki/projects/git-buildpackage/ git-buildpackage]</code> (aka ''gbp'') to maintain Debian/Ubuntu packages with <code>git</code>.
 +
 
 +
General/Reference:
 +
 
 +
* [http://www.debian.org/doc/FAQ/ch-pkg_basics.en.html Basics of the Debian package management system]
 +
* [http://www.debian.org/doc/manuals/maint-guide/index.en.html Debian New Maintainers' Guide]
 +
* [http://cdbs-doc.duckcorp.org/ CDBS Documentation]
 +
 
 +
Python-specific:
 +
 
 +
* [http://wiki.ubuntu.com/PackagingGuide/Complete#Packaging%20Python%20modules%20with%20CDBS Packaging Python modules with CDBS]
 +
* [http://wiki.ubuntu.com/PackagingGuide/Python PackagingGuide/Python]
 +
* [http://showmedo.com/videotutorials/video?name=linuxJensMakingDeb Making a .deb package out of a python program]
  
 
[[Category:Packaging]]
 
[[Category:Packaging]]
 +
[[Category:Python]]

Latest revision as of 11:48, 14 August 2014

Packaging is the process by which pieces of software are turned into installable "packages" for various Linux distributions (and other systems, such as Mac OS X and OLPC).

There are two aspects to this:

  1. Initial creation of the package
  2. Ongoing maintenance as a result of
    • Upstream upgrades
    • Distro upgrades

In this context, "upstream" refers to the original source of the software, before it is packaged. Usually this will be a developer's tarball or source-control repo.

Once a package has been created, the control files that are used to describe and build the package can be re-used for the ongoing maintenance work with very little extra effort. Initial creation and ongoing maintenance may therefore be done by different people.

Further Reading

On this wiki:

  • A tutorial for making packages for Debian-based systems (especially Ubuntu).
  • A guide to using git-buildpackage (aka gbp) to maintain Debian/Ubuntu packages with git.

General/Reference:

Python-specific: