Commit a63f430b authored by Francois-Rene Rideau's avatar Francois-Rene Rideau
Browse files

Editing some more debian files.

parent 9ed5d9fe
As upstream maintainer, I
* use git from the upstream repo
git clone ssh://
* checkout the release branch
git checkout release
* do dark magic to create a release, merging with master,
renumbering the version, then:
git commit
* do the releasing:
git tag 2.00x ; make archive-copy ; make website ;
git tag -f RELEASE ; make push
* edit debian files, then:
git commit
* create debian package:
make debian-package
* if unsatisfied, edit debian files some more then
git commit --amend
then goto previous point.
If ever debian diverges from upstream, you should adapt accordingly.
The below notes are obsolete, but might give you ideas how to do it.
To build this package you need to get the git repository:
git clone git://
......@@ -28,14 +28,14 @@ binary-indep: build
dh_testdir -i
dh_testroot -i
dh_prep -i
chmod +x test/
chmod +x test/
dh_installdirs -i
dh_install -i
#dh_lisp -i
dh_installdocs -i
dh_installinfo -i
dh_installexamples -i
dh_link --verbose -i
dh_strip -i
dh_compress -i
......@@ -46,7 +46,7 @@ binary-indep: build
dh_md5sums -i
dh_builddeb -i
source diff:
source diff:
@echo >&2 'source and diff are obsolete - use dpkg-source -b'; false
binary: binary-indep binary-arch
Markdown is supported
0% or .
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment