Packaging

Differences between revisions 1 and 11 (spanning 10 versions)
⇤ ← Revision 1 as of 2010-01-23 06:42:42 →
Size: 48
Editor: anon-40-149
Comment:
← Revision 11 as of 2010-02-11 07:14:11 → ⇥
Size: 1083
Editor: anon-38-150
Comment:
Deletions are marked like this. Additions are marked like this.
Line 1: Line 1:
Describe SevenMachines/DevHelp/Packaging here. '''[[SevenMachines/DevHelp/Packaging/TheRightWay|Doing It "The Right Way (tm)"!]]'''

Helpful things to know when making a proper debianized package


'''The "Quick Fix Way"'''

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

''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)"!

Helpful things to know when making a proper debianized package

The "Quick Fix Way"

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

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'

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