[Pkg-pagekite-devel] PageKite and Debian (forked from FreedomBox thead)

[Jonas Smedegaard]

On 11-04-26 at 10:59pm, Bjarni Rúnar Einarsson wrote:
> 2011/4/26 Jonas Smedegaard <dr at jones.dk>
> > You are free to package in different ways - I only meant to say that 
> > _I_ work in a specific way, so if you prefer different way than 
> > that, I am not participating (but we can still be friends! :-D ).
> >
> 
> We are both Debian packaging noobs, so your way is as good as any 
> other to us at this point. :-)

Ok.


> We've got a draft package (mostly done by Hrafnkell) which fleshed out 
> some ideas we had about systems integration and the like, but we 
> aren't 100% sure the ideas there conform to Debian best practices and 
> would like some things changed for sure.
> 
>> Do you have tarball releases of upstream code?
> 
> Pagekite.py itself is at this point just a single .py file with no 
> mandatory dependencies aside from Python 2.2+.
> 
> That said, it behaves better with a more recent Python and either 
> pyOpenSSL or python's native ssl are present and some other "optional" 
> things (documentation, config files, the like) have been available 
> from our git repos.  In the experimental debian package (Hrafnkell's 
> fork on git) there is also a man page, init scripts and the like, 
> which I don't know if can be reused or not.
> 
> So perhaps we need to start by defining a .tar.gz distribution which 
> contains everything we think belongs in the .deb ?

That is a bad approach IMO.  Better is to separate upstream code from 
distribution packaging: Compose a tarball as you want the whole wide 
world to consume it.  Redhat, Google, direct users, and Debian alike.

Preferrably stay close to some common release patterns.  Could be the 
GNU patterns (i.e. autotools) or Python gem patterns or whatever.  That 
way you skip a bunch of learning experiences done by a wealth of other 
developers, like using a sub-optimal versioning scheme, or leaving out 
some piece that you didn't think was important but made others not adopt 
your code, etc.


> Are you familiar with CDBS and git-buildpackage, or should we go slow
> > and I introduce you to them while we move along?  Are you familiar 
> > with Debian packaging at all?  Where are we starting off?
> >
> 
> If you have the patience, going slow would be great.  We're both 
> reading about those tools at the moment, but it's a lot to get 
> through.

Ok.

But start with releasing upstream code independent from Debian 
packaging.


 - Jonas

-- 
 * Jonas Smedegaard - idealist & Internet-arkitekt
 * Tlf.: +45 40843136  Website: http://dr.jones.dk/

 [x] quote me freely  [ ] ask before reusing  [ ] keep private
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 836 bytes
Desc: Digital signature
URL: <http://lists.alioth.debian.org/pipermail/pkg-pagekite-devel/attachments/20110427/83c454b1/attachment.pgp>