Note: Currently new registrations are closed, if you want an account Contact us
Difference between revisions of "Learn Debian Packaging"
(Fix links) |
(add section about unpackaged modules) |
||
| Line 23: | Line 23: | ||
* [https://wiki.debian.org/Javascript/Nodejs/Npm2Deb/AdvancedTutorial Advanced tutorial for more complicated modules] | * [https://wiki.debian.org/Javascript/Nodejs/Npm2Deb/AdvancedTutorial Advanced tutorial for more complicated modules] | ||
== Pick an unpackaged but useful module and upload to archive == | |||
* [https://git.fosscommunity.in/debian-ruby/TaskTracker/-/issues/175 List of node dependencies for gitlab] | |||
Revision as of 17:19, 27 January 2021
We are guiding some learners of Free Software Camp to learn Debian Packaging and this page will be used to track the progress of the tasks.
Setting up a Debian Sid environment for packaging
Learn basics of Packaging
Understand the basic concepts using debmake/dh_make (getting source tarballs, creating source package, building the binary package, making it lintian clean)
Once you understand the basic concepts, use npm2deb to automate some of those tasks like getting source tarball, a better debian directory template than the ones created by dh_make/debmake as npm2deb knows more details specific to node modules. You will still have to fix the remaining issues flagged by lintian.
By this time you should know creating lintian clean packages for simple modules and building it in a clean environment like sbuild.
Packaging more complicated modules
Once you get a clear picture of packaging a simple module, we can move to the next stage of packaging more complicated modules that will involve things like, modifying some upstream files, removing some files from source tarball, generating some files from source, getting the source tarball from a git commit etc.