By Date: <-- -->
By Thread: <-- -->

sipXconfig maven2 based build

Damian Krzeminski wrote:
> As a part of effort of cleaning dependencies and making sipXconfig build
> more distro independent (it is java after all) I am experimenting with
> maven2 based build.

Not sure about 'more distro independent'. I couldn't find maven2
packages for most of the distros I've been packaging for lately.


Debian
- no deb, lots of missing dependencies
- Debian ITP has been deleted because of inactivity for more than 600 days
  http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=188782
  http://people.debian.org/~avdyk/maven.html

Ubuntu
- no deb

Gentoo
- maven2 only in testing
  http://packages.gentoo.org/search/?sstring=maven

OpenSuSE
- nothing found


While it's perfectly possible for developers and a 'manual' packager to
install build dependency packages by hand, this is not so for the
automatic build process used by the major distros. A package needs to
have all of its build dependencies available to the distro build host
when the source package is dumped into it.

Relying on unsupported tools makes it extremely difficult (if not
impossible) to get the package into the distro. A package relying on ten
 or so unsupported Java packages will never make it into Debian Sarge.


If we want to support sipX on more distros in the future we probably
need to draw a sheet with current and future build and runtime
dependencies in order to be able to track them and make informed choices
about whether or not we want to introduce them. This would also make it
more efficient to push and track the progress of build dependencies
inclusion in the different distros.


--
mike
_______________________________________________
sipx-dev mailing list
sipx-dev (at) list.sipfoundry.org
List Archive: http://list.sipfoundry.org/archive/sipx-dev