|Deletions are marked like this.||Additions are marked like this.|
|Line 96:||Line 96:|
|1. [[/gitorious|gitorious]] - push the code into team repo (temporary till you get access to pkg-ruby-extras repo on alioth)||1. [[/gitlab|gitlab]] - push the code into team repo (temporary till you get access to pkg-ruby-extras repo on alioth)|
This page will be used to store available information and links which will help to build diaspora and its dependencies for Debian. You can find instructions to test the current version of package from here.
We hang out at #debian-diaspora (on OFTC), so come there if you have any questions.
Regular meetings will take place every Saturday and Sunday at 21:00 IST
Why do you have to package diaspora? - https://github.com/celluloid/celluloid/issues/263#issuecomment-18096685
What does packaging Diaspora for debian mean? - https://joindiaspora.com/posts/2077249
Why do you have to package all the gems? Can't you use rvm? - https://www.loomio.org/discussions/1021#comment-24085
ITP - 597093
Dependency graph - http://people.debian.org/~boutil/diaspora/ (take the latest)
Status updates https://joindiaspora.com/tags/debian-diaspora
Note: Feel free to improve these steps/notes. Add links to more documentation when anything is not clear.
Step 0 - Introduction
Diaspora is written in Ruby language using Rails framework. Diaspora uses many existing ruby libraries and these libraries are distributed as gems. So we need to package all depending gems to package diaspora.
Learn more about rubygems http://www.linuxjournal.com/article/8967
Learn basics of ruby from http://tryruby.org or https://www.ruby-lang.org/en/documentation/quickstart/
Though rubygems itself is a package familiar with ruby developers, we want to provide single method via debian tools (apt/synaptic/software center) for debian users, similar to software written in every other language, so they don't have to learn how each language community distributes their packages.
Learn more about debian package manager called apt (Advanced Packaging Tool) Apt
If you are familiar with C programming you would know the first line of most C programs,
stdio.h is provided by the standard C library (glibc in most GNU/Linux distributions). It provides functions like printf and scanf. Similarly in Ruby, libraries are included by a line like,
It means that particular Ruby program (.rb file) can now use functions provided by rspec library (similar to how you use printf and scanf functions in your C program).
Try installing a gem and see if ruby can find it
gem install vegas gem list irb require 'vegas'
You should see 'true' as output. Press control+d to exit from irb.
Step 1 - Select a Gem
Choose a gem to package from latest pdf file from http://people.debian.org/~boutil/diaspora/ (it has a graph of all dependencies for diaspora). If it has a dependency select that first.
Check if it is already packaged in debian. Search for the package from http://www.debian.org/distrib/packages#search_packages
Check if it is already being worked on by someone else from http://wnpp.debian.net
Note 1: Remember to select ITP from the list and give your gem name as project
Note 2: Debian package names uses '-' instead of '_', prepended with ruby-, unless it is an application (in opposition with libraries, ex: cucumber, rake)
Step 2 - Build a debian package
ITP - say you're going to package something
Initial Build with gem2deb - try building it
- Get your package reviewed and uploaded
gitlab - push the code into team repo (temporary till you get access to pkg-ruby-extras repo on alioth)
upload to mentors - upload it to mentors for sponsors (we usually take directly from git, so this step is not directly required, but is good for you to learn as it applies to a new package in general, you'll need this when you want to upload a package outside this team)
RFS - request a sponsor to upload your package to debian
setting up an environment for building packages - especially a quick-start guide for the ruby folks who want to help with tests and don't want to bother much with packaging part
how to deal with changes in source tarball itself outside of patch/quilt - say you want to take github tarball or you want to remove vendor directory