x11vnc: update to 0.9.14
PATCH 1/1 x11vnc: update to 0.9.14
This uses x11vnc's new upstream location, github, via https. Autoreconf is added, because it's really only a code snapshot release.
--- package/x11vnc/x11vnc.hash | 2 +- package/x11vnc/x11vnc.mk | 9 +++++++-- 2 files changed, 8 insertions(+), 3 deletions(-)
package/x11vnc/x11vnc.hash +1 -1
@@ -1,2 +1,2 @@ # Locally computed: -sha256 f6829f2e629667a5284de62b080b13126a0736499fe47cdb447aedb07a59f13b x11vnc-0.9.13.tar.gz +sha256 45f87c5e4382988c73e8c7891ac2bfb45d8f9ce1196ae06651c84636684ea143 0.9.14.tar.gz
package/x11vnc/x11vnc.mk +7 -2
@@ -4,8 +4,9 @@ # ################################################################################ -X11VNC_VERSION = 0.9.13 -X11VNC_SITE = http://downloads.sourceforge.net/project/libvncserver/x11vnc/$(X11VNC_VERSION) +X11VNC_VERSION = 0.9.14 +X11VNC_SOURCE = $(X11VNC_VERSION).tar.gz +X11VNC_SITE = https://github.com/LibVNC/x11vnc/archive # sdl support is not used in x11vnc, but host include / library search paths # leak in if host has sdl-config X11VNC_CONF_OPTS = --without-sdl
@@ -13,6 +14,10 @@ X11VNC_DEPENDENCIES = xlib_libXt xlib_libXext xlib_libXtst X11VNC_LICENSE = GPL-2.0+ X11VNC_LICENSE_FILES = COPYING +# Upstream moved to github. It's archives don't include a configure script, +# so we need to generate it. +X11VNC_AUTORECONF = YES + ifeq ($(BR2_PACKAGE_AVAHI_DAEMON)$(BR2_PACKAGE_DBUS),yy) X11VNC_DEPENDENCIES += avahi dbus else
Signature · 1 line
2.1.4
PATCH 1/1 x11vnc: update to 0.9.14
Quoted 14 lines · Martin Kepplinger
This uses x11vnc's new upstream location, github, via https. Autoreconf is added, because it's really only a code snapshot release.
Signed-off-by Martin Kepplinger <[email protected]>--- package/x11vnc/x11vnc.hash | 2 +- package/x11vnc/x11vnc.mk | 9 +++++++-- 2 files changed, 8 insertions(+), 3 deletions(-)package/x11vnc/x11vnc.hash +0
-0
package/x11vnc/x11vnc.hash line 2
Quoted 3 lines
package/x11vnc/x11vnc.hash +1
-1@@ -1,2 +1,2 @@ # Locally computed: -sha256 f6829f2e629667a5284de62b080b13126a0736499fe47cdb447aedb07a59f13b x11vnc-0.9.13.tar.gz +sha256 45f87c5e4382988c73e8c7891ac2bfb45d8f9ce1196ae06651c84636684ea143 0.9.14.tar.gz
It's ugly to have 0.9.14.tar.gz. Is there a buildroot-style solution to this?
And other than that, is there a reason why x11vnc had not been updated before? 0.9.14 is one and a half years old.
thanks
martin
PATCH 1/1 x11vnc: update to 0.9.14
Hi Martin,
Quoted 10 lines · Martin Kepplinger
Quoted 9 lines · Martin Kepplinger
This uses x11vnc's new upstream location, github, via https. Autoreconf is added, because it's really only a code snapshot release.
Signed-off-by Martin Kepplinger <[email protected]>--- package/x11vnc/x11vnc.hash | 2 +- package/x11vnc/x11vnc.mk | 9 +++++++-- 2 files changed, 8 insertions(+), 3 deletions(-)
Quoted 12 lines
package/x11vnc/x11vnc.hash line 2
Quoted 8 lines
package/x11vnc/x11vnc.hash +1
-1@@ -1,2 +1,2 @@ # Locally computed: -sha256 f6829f2e629667a5284de62b080b13126a0736499fe47cdb447aedb07a59f13b x11vnc-0.9.13.tar.gz +sha256 45f87c5e4382988c73e8c7891ac2bfb45d8f9ce1196ae06651c84636684ea143 0.9.14.tar.gzIt's ugly to have 0.9.14.tar.gz. Is there a buildroot-style solution to this?
This is just fine, it's not the only package whose tarball name doesn't include the package name. Look for instance the mpv and yaffs2utils packages.
Quoted 3 lines
And other than that, is there a reason why x11vnc had not been updated before? 0.9.14 is one and a half years old.
Because nobody did it, probably. Anyway, the 0.9.14 is considered a bleeding edge development release (according to x11vnc's website) and even with that, as you said, is one and a half years old. Just wondering..., shouldn't be better to go with ToT (top of the tree) instead?
X11VNC_VERSION = e47d922d4a4d980f8dce3e466c73dc4665e4bc01 X11VNC_SITE = $(call github,LibVNC,x11vnc,$(X11VNC_VERSION))
Regards,
Vincent
Quoted 9 lines
thanks
martin
_______________________________________________
buildroot mailing list
buildroot at busybox.net
http://lists.busybox.net/mailman/listinfo/buildroot
PATCH 1/1 x11vnc: update to 0.9.14
Quoted 34 lines · Vicente Olivert Riera
Hi Martin,
Quoted 10 lines · Martin Kepplinger
Quoted 9 lines · Martin Kepplinger
This uses x11vnc's new upstream location, github, via https. Autoreconf is added, because it's really only a code snapshot release.
Signed-off-by Martin Kepplinger <[email protected]>--- package/x11vnc/x11vnc.hash | 2 +- package/x11vnc/x11vnc.mk | 9 +++++++-- 2 files changed, 8 insertions(+), 3 deletions(-)Quoted 12 lines
package/x11vnc/x11vnc.hash line 2
Quoted 8 lines
package/x11vnc/x11vnc.hash +1
-1@@ -1,2 +1,2 @@ # Locally computed: -sha256 f6829f2e629667a5284de62b080b13126a0736499fe47cdb447aedb07a59f13b x11vnc-0.9.13.tar.gz +sha256 45f87c5e4382988c73e8c7891ac2bfb45d8f9ce1196ae06651c84636684ea143 0.9.14.tar.gzIt's ugly to have 0.9.14.tar.gz. Is there a buildroot-style solution to this?
This is just fine, it's not the only package whose tarball name doesn't include the package name. Look for instance the mpv and yaffs2utils packages.
Quoted 3 lines
And other than that, is there a reason why x11vnc had not been updated before? 0.9.14 is one and a half years old.
Quoted 8 lines
Because nobody did it, probably. Anyway, the 0.9.14 is considered a bleeding edge development release (according to x11vnc's website) and even with that, as you said, is one and a half years old. Just wondering..., shouldn't be better to go with ToT (top of the tree) instead?
X11VNC_VERSION=e47d922d4a4d980f8dce3e466c73dc4665e4bc01X11VNC_SITE= $(call github,LibVNC,x11vnc,$(X11VNC_VERSION))
They don't seem to use development branches; While I think it would be fine to use the master branch, just from my personal feeling I'd use the tagged versions. Seems like the project is maintained and 0.9.15 somehow on the horizon sometime sooner or later.
Quoted 13 lines
Regards,
Vincent
Quoted 9 lines
thanks
martin
_______________________________________________
buildroot mailing list
buildroot at busybox.net
http://lists.busybox.net/mailman/listinfo/buildroot
PATCH 1/1 x11vnc: update to 0.9.14
Quoted 16 lines · Martin Kepplinger
Quoted 13 lines · Vicente Olivert Riera
Hi Martin,
Quoted 10 lines · Martin Kepplinger
Quoted 9 lines · Martin Kepplinger
This uses x11vnc's new upstream location, github, via https. Autoreconf is added, because it's really only a code snapshot release.
Signed-off-by Martin Kepplinger <[email protected]>--- package/x11vnc/x11vnc.hash | 2 +- package/x11vnc/x11vnc.mk | 9 +++++++-- 2 files changed, 8 insertions(+), 3 deletions(-)
Quoted 12 lines
Quoted 4 lines
Quoted 4 lines
Quoted 4 lines
package/x11vnc/x11vnc.hash +0
-0Quoted 8 lines
Quoted 8 lines
package/x11vnc/x11vnc.hash line 2
Quoted 4 lines
package/x11vnc/x11vnc.hash +1
-1@@ -1,2 +1,2 @@ # Locally computed: -sha256 f6829f2e629667a5284de62b080b13126a0736499fe47cdb447aedb07a59f13b x11vnc-0.9.13.tar.gz +sha256 45f87c5e4382988c73e8c7891ac2bfb45d8f9ce1196ae06651c84636684ea143 0.9.14.tar.gzIt's ugly to have 0.9.14.tar.gz. Is there a buildroot-style solution to this?
Yes, the github helper. If the link contains 'archive', it's for the github
helper. If it contains 'releases', it's an uploaded tarball and you should use the expanded URL.
Quoted 13 lines
Quoted 13 lines
This is just fine, it's not the only package whose tarball name doesn't include the package name. Look for instance the mpv and yaffs2utils packages.
Quoted 3 lines
And other than that, is there a reason why x11vnc had not been updated before? 0.9.14 is one and a half years old.
Because nobody did it, probably. Anyway, the 0.9.14 is considered a bleeding edge development release (according to x11vnc's website) and even with that, as you said, is one and a half years old. Just wondering..., shouldn't be better to go with ToT (top of the tree) instead?
Quoted 8 lines
Quoted 3 lines
X11VNC_VERSION=e47d922d4a4d980f8dce3e466c73dc4665e4bc01X11VNC_SITE= $(call github,LibVNC,x11vnc,$(X11VNC_VERSION))They don't seem to use development branches; While I think it would be fine to use the master branch, just from my personal feeling I'd use the tagged versions. Seems like the project is maintained and 0.9.15 somehow on the horizon sometime sooner or later.
We indeed prefer to stick to officially released versions when upstream has
them. And we generally don't like to take releases that upstream considers a development/alpha/... release.
Is there a reason why you need this bump?
Regards,
Arnout
Signature · 6 lines
Arnout Vandecappelle arnout at mind be Senior Embedded Software Architect +32-16-286500 Essensium/Mind http://www.mind.be G.Geenslaan 9, 3001 Leuven, Belgium BE 872 984 063 RPR Leuven LinkedIn profile: http://www.linkedin.com/in/arnoutvandecappelle GPG fingerprint: 7493 020B C7E3 8618 8DEC 222C 82EB F404 F9AC 0DDF
PATCH 1/1 x11vnc: update to 0.9.14
Quoted 32 lines · Arnout Vandecappelle
Quoted 16 lines · Martin Kepplinger
Quoted 13 lines · Vicente Olivert Riera
Hi Martin,
Quoted 10 lines · Martin Kepplinger
Quoted 9 lines · Martin Kepplinger
This uses x11vnc's new upstream location, github, via https. Autoreconf is added, because it's really only a code snapshot release.
Signed-off-by Martin Kepplinger <[email protected]>--- package/x11vnc/x11vnc.hash | 2 +- package/x11vnc/x11vnc.mk | 9 +++++++-- 2 files changed, 8 insertions(+), 3 deletions(-)Quoted 12 lines
Quoted 4 lines
Quoted 4 lines
Quoted 4 lines
package/x11vnc/x11vnc.hash +0
-0Quoted 8 lines
Quoted 8 lines
package/x11vnc/x11vnc.hash line 2
Quoted 4 lines
package/x11vnc/x11vnc.hash +1
-1@@ -1,2 +1,2 @@ # Locally computed: -sha256 f6829f2e629667a5284de62b080b13126a0736499fe47cdb447aedb07a59f13b x11vnc-0.9.13.tar.gz +sha256 45f87c5e4382988c73e8c7891ac2bfb45d8f9ce1196ae06651c84636684ea143 0.9.14.tar.gzIt's ugly to have 0.9.14.tar.gz. Is there a buildroot-style solution to this?
Quoted 3 lines
Yes, the github helper. If the link contains 'archive', it's for the github
helper. If it contains 'releases', it's an uploaded tarball and you should use the expanded URL.
thanks.
Quoted 24 lines
Quoted 15 lines
Quoted 15 lines
This is just fine, it's not the only package whose tarball name doesn't include the package name. Look for instance the mpv and yaffs2utils packages.
Quoted 3 lines
And other than that, is there a reason why x11vnc had not been updated before? 0.9.14 is one and a half years old.
Because nobody did it, probably. Anyway, the 0.9.14 is considered a bleeding edge development release (according to x11vnc's website) and even with that, as you said, is one and a half years old. Just wondering..., shouldn't be better to go with ToT (top of the tree) instead?
Quoted 8 lines
Quoted 3 lines
X11VNC_VERSION=e47d922d4a4d980f8dce3e466c73dc4665e4bc01X11VNC_SITE= $(call github,LibVNC,x11vnc,$(X11VNC_VERSION))They don't seem to use development branches; While I think it would be fine to use the master branch, just from my personal feeling I'd use the tagged versions. Seems like the project is maintained and 0.9.15 somehow on the horizon sometime sooner or later.
Quoted 5 lines
We indeed prefer to stick to officially released versions when upstream has
them. And we generally don't like to take releases that upstream considers a development/alpha/... release.Is there a reason why you need this bump?
Actually, no. There'd be a reason for me to have the next release. I just thought to update in order to make it easier for 0.9.15. Let's leave it as it is. I'll propose an update to 0.9.15 when released and tested.
martin
Quoted 5 lines
Regards,
Arnout
PATCH 1/1 x11vnc: update to 0.9.14
In reply to Arnout VandecappelleHello,
Quoted 1 line · Arnout Vandecappelle
Is there a reason why you need this bump?
Well, do we need a reason to bump a package, other than "upstream has a new release, possibly with new features/bug fixes" ? Tons of version bumps we merged are not motivated by a specific reason, other than making sure Buildroot uses recent versions of the different components.
Best regards,
Thomas
Signature · 3 lines
Thomas Petazzoni, CTO, Free Electrons Embedded Linux and Kernel engineering http://free-electrons.com
PATCH v2 1/1 x11vnc: update to 0.9.14
This uses x11vnc's new upstream location at github. Autoreconf is added because it's really only a code snapshot release.
---
In the end you're right and there's nothing special here. Without any reason, buildroot doesn't hold on an old version. People do releases. People break stuff. People fix stuff. Since I happen to need a fix in the upcoming 0.9.15 this is probably more reason to randomly update than other updates have.
... I tested it. For me, using Xfbdev, this 0.9.14 works just fine :)
revision history
----------------
v2: use the github helper instead of a URL
v1: initial proposal to update 0.9.13 to 0.9.14
package/x11vnc/x11vnc.hash | 2 +- package/x11vnc/x11vnc.mk | 6 ++++-- 2 files changed, 5 insertions(+), 3 deletions(-)
package/x11vnc/x11vnc.hash +1 -1
@@ -1,2 +1,2 @@ # Locally computed: -sha256 f6829f2e629667a5284de62b080b13126a0736499fe47cdb447aedb07a59f13b x11vnc-0.9.13.tar.gz +sha256 45f87c5e4382988c73e8c7891ac2bfb45d8f9ce1196ae06651c84636684ea143 x11vnc-0.9.14.tar.gz
package/x11vnc/x11vnc.mk +4 -2
@@ -4,8 +4,8 @@ # ################################################################################ -X11VNC_VERSION = 0.9.13 -X11VNC_SITE = http://downloads.sourceforge.net/project/libvncserver/x11vnc/$(X11VNC_VERSION) +X11VNC_VERSION = 0.9.14 +X11VNC_SITE = $(call github,LibVNC,x11vnc,$(X11VNC_VERSION)) # sdl support is not used in x11vnc, but host include / library search paths # leak in if host has sdl-config X11VNC_CONF_OPTS = --without-sdl
@@ -13,6 +13,8 @@ X11VNC_DEPENDENCIES = xlib_libXt xlib_libXext xlib_libXtst X11VNC_LICENSE = GPL-2.0+ X11VNC_LICENSE_FILES = COPYING +X11VNC_AUTORECONF = YES + ifeq ($(BR2_PACKAGE_AVAHI_DAEMON)$(BR2_PACKAGE_DBUS),yy) X11VNC_DEPENDENCIES += avahi dbus else
Signature · 1 line
2.1.4
PATCH v2 1/1 x11vnc: update to 0.9.14
Quoted 11 lines · Martin Kepplinger
This uses x11vnc's new upstream location at github. Autoreconf is added because it's really only a code snapshot release.
Signed-off-by Martin Kepplinger <[email protected]>---
In the end you're right and there's nothing special here. Without any reason, buildroot doesn't hold on an old version. People do releases. People break stuff. People fix stuff. Since I happen to need a fix in the upcoming 0.9.15 this is probably more reason to randomly update than other updates have.
Quoted 8 lines
... I tested it. For me, using Xfbdev, this 0.9.14 works just fine :)
revision history
----------------
v2: use the github helper instead of a URL
v1: initial proposal to update 0.9.13 to 0.9.14
Any objections? What *is* to note here maybe, is that with 0.9.14 they renamed their x11vnc souce directory to src internally. In case people have patches, they need to be adapted. But again, that's nothing special here :)
thanks
martin
PATCH v2 1/1 x11vnc: update to 0.9.14
In reply to Martin KepplingerHi Martin,
Quoted 48 lines · Martin Kepplinger
This uses x11vnc's new upstream location at github. Autoreconf is added because it's really only a code snapshot release.
Signed-off-by Martin Kepplinger <[email protected]>---
In the end you're right and there's nothing special here. Without any reason, buildroot doesn't hold on an old version. People do releases. People break stuff. People fix stuff. Since I happen to need a fix in the upcoming 0.9.15 this is probably more reason to randomly update than other updates have.
... I tested it. For me, using Xfbdev, this 0.9.14 works just fine :)
revision history
----------------
v2: use the github helper instead of a URL
v1: initial proposal to update 0.9.13 to 0.9.14package/x11vnc/x11vnc.hash | 2 +- package/x11vnc/x11vnc.mk | 6 ++++-- 2 files changed, 5 insertions(+), 3 deletions(-)package/x11vnc/x11vnc.hash +1
-1@@ -1,2 +1,2 @@ # Locally computed: -sha256 f6829f2e629667a5284de62b080b13126a0736499fe47cdb447aedb07a59f13b x11vnc-0.9.13.tar.gz +sha256 45f87c5e4382988c73e8c7891ac2bfb45d8f9ce1196ae06651c84636684ea143 x11vnc-0.9.14.tar.gzpackage/x11vnc/x11vnc.mk +2
-2@@ -4,8 +4,8 @@ # ################################################################################ -X11VNC_VERSION = 0.9.13 -X11VNC_SITE = http://downloads.sourceforge.net/project/libvncserver/x11vnc/$(X11VNC_VERSION) +X11VNC_VERSION = 0.9.14 +X11VNC_SITE = $(call github,LibVNC,x11vnc,$(X11VNC_VERSION)) # sdl support is not used in x11vnc, but host include / library search paths # leak in if host has sdl-config X11VNC_CONF_OPTS = --without-sdl
package/x11vnc/x11vnc.mk X11VNC_DEPENDENCIES = xlib_libXt xlib_libXext xlib_libXtst · line 16
Quoted 4 lines
package/x11vnc/x11vnc.mk +1
-0@@ -13,6 +13,8 @@ X11VNC_DEPENDENCIES = xlib_libXt xlib_libXext xlib_libXtst X11VNC_LICENSE = GPL-2.0+ X11VNC_LICENSE_FILES = COPYING +X11VNC_AUTORECONF = YES
Please add a comment above it:
# Source coming from github, no configure included
If you resubmit, you can add my
Regards,
Arnout
Quoted 5 lines
package/x11vnc/x11vnc.mk +1
-0+ ifeq ($(BR2_PACKAGE_AVAHI_DAEMON)$(BR2_PACKAGE_DBUS),yy) X11VNC_DEPENDENCIES += avahi dbus else
Signature · 6 lines
Arnout Vandecappelle arnout at mind be Senior Embedded Software Architect +32-16-286500 Essensium/Mind http://www.mind.be G.Geenslaan 9, 3001 Leuven, Belgium BE 872 984 063 RPR Leuven LinkedIn profile: http://www.linkedin.com/in/arnoutvandecappelle GPG fingerprint: 7493 020B C7E3 8618 8DEC 222C 82EB F404 F9AC 0DDF
PATCH v3 1/1 x11vnc: update to 0.9.14
This switches to x11vnc's new upstream location at github. Autoreconf is added because it's only a code snapshot release. Subsequent releases will most probably look the same, see
https://github.com/LibVNC/x11vnc/issues/35#issuecomment-297474900
---
redone the patch. As mentioned earlier, I at least did a test-run with this version. And 0.9.15 is indeed in the works, see
https://github.com/LibVNC/x11vnc/milestone/2 :)
revision history
----------------
v3: add a comment, why AUTORECONF is added; thanks Arnout Vandecappelle
v2: use the github helper instead of a URL
v1: initial proposal to update 0.9.13 to 0.9.14
package/x11vnc/x11vnc.hash | 2 +- package/x11vnc/x11vnc.mk | 7 +++++-- 2 files changed, 6 insertions(+), 3 deletions(-)
package/x11vnc/x11vnc.hash +1 -1
@@ -1,2 +1,2 @@ # Locally computed: -sha256 f6829f2e629667a5284de62b080b13126a0736499fe47cdb447aedb07a59f13b x11vnc-0.9.13.tar.gz +sha256 45f87c5e4382988c73e8c7891ac2bfb45d8f9ce1196ae06651c84636684ea143 x11vnc-0.9.14.tar.gz
package/x11vnc/x11vnc.mk +5 -2
@@ -4,8 +4,8 @@ # ################################################################################ -X11VNC_VERSION = 0.9.13 -X11VNC_SITE = http://downloads.sourceforge.net/project/libvncserver/x11vnc/$(X11VNC_VERSION) +X11VNC_VERSION = 0.9.14 +X11VNC_SITE = $(call github,LibVNC,x11vnc,$(X11VNC_VERSION)) # sdl support is not used in x11vnc, but host include / library search paths # leak in if host has sdl-config X11VNC_CONF_OPTS = --without-sdl
@@ -13,6 +13,9 @@ X11VNC_DEPENDENCIES = xlib_libXt xlib_libXext xlib_libXtst X11VNC_LICENSE = GPL-2.0+ X11VNC_LICENSE_FILES = COPYING +# Source coming from github, no configure included +X11VNC_AUTORECONF = YES + ifeq ($(BR2_PACKAGE_AVAHI_DAEMON)$(BR2_PACKAGE_DBUS),yy) X11VNC_DEPENDENCIES += avahi dbus else
Signature · 1 line
2.11.0
Thomas Petazzoni
AppliedPATCH v3 1/1 x11vnc: update to 0.9.14
Hello,
Quoted 8 lines · Martin Kepplinger
This switches to x11vnc's new upstream location at github. Autoreconf is added because it's only a code snapshot release. Subsequent releases will most probably look the same, see
https://github.com/LibVNC/x11vnc/issues/35#issuecomment-297474900Signed-off-by Martin Kepplinger <[email protected]>---
Applied to master, thanks. Since you are interested in x11vnc, can you add yourself as a developer for this package in the DEVELOPERS file ?
Thanks a lot!
Thomas
Signature · 3 lines
Thomas Petazzoni, CTO, Free Electrons Embedded Linux, Kernel and Android engineering http://free-electrons.com
PATCH 1/1 x11vnc: update to 0.9.14
In reply to Thomas PetazzoniQuoted 10 lines · Thomas Petazzoni
Hello,
Quoted 1 line · Arnout Vandecappelle
Is there a reason why you need this bump?
Well, do we need a reason to bump a package, other than "upstream has a new release, possibly with new features/bug fixes" ? Tons of version bumps we merged are not motivated by a specific reason, other than making sure Buildroot uses recent versions of the different components.
Why did you remove the part that explains exactly this?
Quoted 4 lines
Quoted 4 lines · Arnout Vandecappelle
Quoted 3 lines
We indeed prefer to stick to officially released versions when upstream has
them. And we generally don't like to take releases that upstream considers a development/alpha/... release.
Quoting the x11vnc website [1]:
-----
As of Sep 2011, the x11vnc-0.9.13.tar.gz source package is released (recommended download). [...] Also, you can get a copy of my latest, bleeding edge x11vnc-0.9.14-dev.tar.gz tarball to build the most up to date one.
-----
However, I didn't actually read that website before, I just read Vicente's
comment. If I had read the website, I would have noticed that it refers to a -dev tarball, and that at the time it was expected that a real release would happen end of 2011.
With that in mind, I think we can conclude that the website is simply out of
date and should be relied on, and that there is no reason not to bump to 0.9.14.
Regards,
Arnout
Signature · 6 lines
Arnout Vandecappelle arnout at mind be Senior Embedded Software Architect +32-16-286500 Essensium/Mind http://www.mind.be G.Geenslaan 9, 3001 Leuven, Belgium BE 872 984 063 RPR Leuven LinkedIn profile: http://www.linkedin.com/in/arnoutvandecappelle GPG fingerprint: 7493 020B C7E3 8618 8DEC 222C 82EB F404 F9AC 0DDF