[Pkg-crosswire-devel] Packaging Project Planning

Dmitrijs Ledkovs dmitrij.ledkov at gmail.com
Tue May 19 21:12:16 BST 2009

What do we want to achieve before uploading to unstable?

Are we repackaging it or not? If yes, what are we gonna remove from the tarball?

I would want to double check that doc-base works

Bibledit? Bibletime?

Before we upload I would love to try rebuilding everything in Lenny &
Sid and testing the debs with piuparts

After reading up blog posts about debhelper7 I was very temted to try
it out. it is very neat. The best stuff I like about it is everything
is in manpages _and_ it has cdbs style where everything is autoguess
and you can override whatever you need.[1, 2] On support side
debhelper is in Lenny and in Hardy backports. For hardy ppa there are
two options either enable -backports which might bring in newer
dependencies which are not necesserly installed / wanted on the Hardy
machines out there. Or alternativly upload debhelper7 to our ppa to
enable one-off backport (fake "apt pinning").

Lenny NOW
There are no PPA's for lenny. I've manage to create download's area on
our "crosswire" project on launchpad shall we upload alpha lenny debs
there? Cause there was a request for Lenny debs today.....

[1] http://kitenet.net/~joey/blog/entry/cdbs_killer___40__design_phase__41__/

[2] $ man debhelper dh dh_auto_install dh_auto_build

With best regards

Dmitrijs Ledkovs (for short Dima),
Ледков Дмитрий Юрьевич

More information about the Pkg-crosswire-devel mailing list