Bug#627362: [jitsi-dev] Re: Git for jitsi, native Debian package?
Hi Emil,
by looking for free software alternatives for Skype available on Debian, I got
aware of jitsi, which seems to have an awesome feature set. As it is not
available in the official Debian archive, I looked around and found out about
the recent efforts to package it for Debian (namely Debian bug #627362).
On Tue, Nov 22, 2011 at 04:58:34PM +0100, Emil Ivov wrote:
> On Tue, Nov 22, 2011 at 4:09 PM, Thomas Koch <thomas@koch.ro> wrote:
> > In any case, there are some things that Jitsi should/could/must do itself to
> > make a native package for Debian/Fedora/OpenSuse doable. I've opened jira
> > issues for those and linked them from an umbrella issue:
> >
> > http://java.net/jira/browse/JITSI-996
>
> Ouch ... that's something that we like to avoid [0].
>
> We only enter issues once we've determined exactly what they are and
> decided that we'll be fixing them at some point. I've closed the
> issues and we'll reopen those that we agree on, if and when we do.
> Right now we are still in the discussion stages of the debian
> packaging. We'd first need to decide exactly what needs to be resolved
> here and how we can do that.
> [...]
>
> > We can continue to discuss the items separately in those issues.
Okay, so, let's list all the issues that Thomas reported already, here again.
For one to make them more visible, and also to get a consensus about the status
of these issues. Not using an issue tracker will of course make it harder to
keep track of the actual conclusions. But as you wanted to have it this way,
of course I expect that you will then give your opinion on them one by one,
more with regards to content than with regards the way we report issues.
-----------------------------------------------------------------------------
JITSI-995 document (or manage) native dependencies (by Thomas Koch)
There's no central location where one can see which C libraries of what
version, origin and license Jitsi uses, which of them are patched, in what way
and for what reason.
I'm not a C developer so I don't know if there's something like Maven/Ivy for
C that manages dependencies?
-----------------------------------------------------------------------------
JITSI-994 Use Ivy or Maven to manage java dependencies (by Thomas Koch)
It is hard for a distro (Debian/Fedora/Suse) packager to find out which java
dependencies Jitsi has. A pom.xml or ivy.xml would make things much easier
and then the dependencies could also be removed from SVN.
-----------------------------------------------------------------------------
JITSI-993 get rid of json.org java dependency (by Thomas Koch)
The json.org java library is non-free according to Debian and maybe also
other distros. As long as jitsi depends on json.org it can not enter the
Debian archive.
http://www.mail-archive.com/debian-legal@lists.debian.org/msg40718.html
-----------------------------------------------------------------------------
JITSI-997 Provide a source only tarball (by Thomas Koch)
Linux distributions want to build their packages and all dependencies of
those themselves. So it must be possible to download a source distribution of
jitsi (prefarable as .tar.gz or .tar.bz2) that does not contain any
third-party binaries and build jitsi from this source distribution with the
help of the dependencies existing in the distro.
-----------------------------------------------------------------------------
JITSI-998 review and document licenses and origins of images in jitsi
(by Thomas Koch)
A distro packager needs to be sure that the images coming with Jitsi can be
distributed under a free license. If the images are taken from common sets
like Tango it would even be preferable for a packager to not ship the images
in the jitsi package but to depend on the tango package of the distribution.
-----------------------------------------------------------------------------
I am looking forward to read your comments on these issues.
Regards,
Micha
Reply to: