Packaging
Differences between revisions 10 and 13 (spanning 3 versions)
|
Size: 1051
Comment:
|
Size: 367
Comment:
|
| Deletions are marked like this. | Additions are marked like this. |
| Line 1: | Line 1: |
| '''[[TheRightWay|Doing It "The Right Way (tm)"!]]''' | '''[[SevenMachines/DevHelp/Packaging/TheRightWay|Doing It "The Right Way (tm)"!]]''' :D |
| Line 6: | Line 6: |
| '''The "Quick Fix Way"''' | '''[[SevenMachines/DevHelp/Packaging/TheQuickFixWay|The "Quick Fix Way"]]''' :\ |
| Line 9: | 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)"!
Helpful things to know when making a proper debianized package
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)