sofia-sip packaging considerations

[George Danchev]

On Thursday 15 June 2006 21:28, Kilian Krause wrote:
> Hi guys,
>
> > > 	1) -bin package - I have a binary package sofia-sip which content
> > > binary executable suitable for development and test purposes. I think
> > > it best to be named sofia-sip-bin, what do you think ?
> >
> > Yes, I think -bin is fine..
>
> as there is no other sofia-sip binary or virtual package around, what's
> the purpose of naming it -bin? I guess if the software is named
> "sofia-sip" then people would expect to be able to install it as such,
> wouldn't they?

It is more consistent with other package already in the archive:

chmlib-bin
libadns1-bin
libarts1-bin
libcap-bin
libcap2-bin
libdirectfb-bin
libdv-bin
libforms-bin
libgnome2-bin
libgnomeprint-bin
libgpib-bin
libgtk2.0-bin
libgtkmathview-bin
libjconv-bin
libktoblzcheck-bin
libocamlodbc-ocaml-bin
libotf-bin
libotr1-bin
librsvg2-bin
libruli-bin
libtrain-bin
libtunepimp-bin
libungif-bin
libwmf-bin
libxbase2.0-bin
libxbsql-bin
zziplib-bin

Try ara -i ;-)
& #list /^lib/ and /bin$/


> Morevoer, Kai, what's your help to be expected with the debian
> packaging? As packaging with a "good upstream" is pretty much a one time
> task, I don't really see the point of having too many people in the
> pkg-voip group who are not primarily active developers for the voip
> packges. I know we have the air to be a large group of developers, yet
> things are sometimes a bit slowly in pkg-voip. Therefore I think if you
> agree that we should now get sofia-sip in shape for Debian, then we'll
> just do this via the mailinglist and regular patches.
>
> In case you disagree, feel free to convince me that SVN access for you
> is going to help with the development and you'll have it in no time.

Sorry for the confusion, but the truth is that it is me who is requesting 
Kai's svn access. My justifications are: 

* He is really aware of debian packaging (see the sofia-sip changelog for his 
work) and could serve as sofia-sip maintainer when we are really short of 
time since he is aware of both the library itsef and packaing.

* The library is the first step, then come some applications related to that 
library, which he is also aware of (as being co-developer or woking closely 
upstream) like 
http://telepathy.freedesktop.org/
http://tapioca-voip.sourceforge.net/
http://farsight.sf.net/
and some more... 

I do not know how much time will these consume... 

* Yes I know we are not after to have every upstream added to pkg-voip repo, 
but I am requesting his help as Debian package maintainer ;-)

* We can live without his help, but I believe it will be easier and faster to 
get the things done when having such debianized upstream maintainers next to 
us ;-)

-- 
pub 4096R/0E4BD0AB 2003-03-18 <people.fccf.net/danchev/key pgp.mit.edu>
fingerprint 1AE7 7C66 0A26 5BFF DF22 5D55 1C57 0C89 0E4B D0AB