Packaging
|
Size: 1327
Comment:
|
Size: 1083
Comment:
|
| Deletions are marked like this. | Additions are marked like this. |
| Line 1: | Line 1: |
| there are probably a few different sources i'd recommend to learn about packaging | '''[[SevenMachines/DevHelp/Packaging/TheRightWay|Doing It "The Right Way (tm)"!]]''' |
| Line 3: | Line 3: |
| 1. '''[[https://wiki.ubuntu.com/PackagingGuide/Complete|The Ubuntu Packaging Guide ]]''' | Helpful things to know when making a proper debianized package |
| Line 5: | Line 5: |
| 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 | |
| Line 7: | Line 6: |
| 2. '''[[http://www.debian.org/doc/maint-guide/|The Debian New Maintainers Guide ]]''' | '''The "Quick Fix Way"''' |
| Line 9: | Line 8: |
| Much more comprehensive, a good read but also a good reference when you're looking for a specific explanation of something | When you only need to use packaging to do some basic handling of installing/uninstalling source code on your local machine |
| Line 11: | Line 10: |
| 3. '''Source Packages''' | ''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 |
| Line 13: | Line 12: |
| 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 |
For example, a typical gnu-type compilation process might look something like this |
| Line 17: | Line 14: |
| 4. '''[[https://wiki.ubuntu.com/UbuntuDeveloperWeek/|Ubuntu Developer Week]]''' | -configure build for this system $./configure |
| Line 19: | Line 17: |
| 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]] |
- 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)