Packaging

Differences between revisions 9 and 13 (spanning 4 versions)
⇤ ← Revision 9 as of 2010-02-11 07:10:14 →
Size: 2457
Editor: anon-38-150
Comment:
← Revision 13 as of 2010-02-11 07:34:43 → ⇥
Size: 367
Editor: anon-38-150
Comment:
Deletions are marked like this. Additions are marked like this.
Line 1: Line 1:
'''Doing It "The Right Way (tm)"!''' '''[[SevenMachines/DevHelp/Packaging/TheRightWay|Doing It "The Right Way (tm)"!]]''' :D
Line 5: Line 5:
1. ''[[https://wiki.ubuntu.com/PackagingGuide/Complete|The Ubuntu Packaging Guide ]]''
Line 7: Line 6:
I'd probably say this is the best place to start, it's really good! The right amount of detail explained with a good deal of clarity

2. ''[[http://www.debian.org/doc/maint-guide/|The Debian New Maintainers Guide ]]''

Much more comprehensive, a good read but also a good reference when you're looking for a specific explanation of something

3. ''Source Packages''

With something in the region of 30,000 packages in ubuntu, if you want to package something theres more than likely going to be similar packages already in the repository. If you can find some then why not look at what others with similar programs have done,
$apt-get source someprogram
then rifle through their packaging, see if it suits your needs, and if so, use it as the basis for your own package

4. ''[[https://wiki.ubuntu.com/UbuntuDeveloperWeek/|Ubuntu Developer Week]]''

Why not learn from the experts!, there will be classes to help get started with packaging (and lots of other things)
Previous developer weeks are archived so you can try them out when you have free time [[https://wiki.ubuntu.com/UbuntuDeveloperWeek/Previous|from the archives]]


''More Useful Links''

'''[[http://cdbs-doc.duckcorp.org/en/cdbs-doc.xhtml|CDBS]]''' - Keep it simple and let the common debian build system deal with the finer points of packaging

'''The "Quick Fix Way"'''		 '''[[SevenMachines/DevHelp/Packaging/TheQuickFixWay|The "Quick Fix Way"]]''' :\
Line 32: Line 9:

''Checkinstall'' - This handy program acts as a kind of wrapper around the source codes build system and creates a simple package that the packaging system can use to install and uninstall compiled source

For example, a typical gnu-type compilation process might look something like this

-configure build for this system
$./configure

- compile the program
$make

- install the program
$make install

Checkinstall replaces the last step, it pretends to run 'make install' inside of a fake installation environment, sees what files go where, and then creates a package that does the same thing.
Essentially this means that the package management system can handle installing and removing your compiled program instead of 'make install' / 'make uninstall'

Doing It "The Right Way (tm)"! Big Grin :)

Helpful things to know when making a proper debianized package

The "Quick Fix Way" Confused :\

When you only need to use packaging to do some basic handling of installing/uninstalling source code on your local machine

SevenMachines/DevHelp/Packaging (last edited 2010-02-18 09:57:01 by 94-193-93-142)