Re: Cloudstack for Debian

2014-12-16 Thread Michael Meskes
[Sorry for my late answering, I've been travelling quite a bit too much.] > Great! I'm not an expert at packaging for Debian. I created the > packaging because we needed it, but it's not perfect. > > The main problem now is that we include all kinds of JAR files in our > packages which isn't idea

Re: Cloudstack for Debian

2014-11-20 Thread Thomas Goirand
On 11/19/2014 11:40 PM, Martin Zobel-Helas wrote: > Hi, > > On Wed Nov 19, 2014 at 14:55:51 +0100, Michael Meskes wrote: >> Hi, >> >> Wido and I have been talking about bringing Cloudstack into Debian. >> There is quite a bit of work involved because several dependencies are >> not yet packaged.

Re: Cloudstack for Debian

2014-11-20 Thread Wido den Hollander
On 11/19/2014 05:00 PM, Emmanuel Bourg wrote: > Le 19/11/2014 14:55, Michael Meskes a écrit : > >> Also, as a bonus question to the Debian folks, should we try >> establishing a cloudstack packaging group or do we push the effort into >> the java packaging group? > > Cloudstack is more than wel

Re: Cloudstack for Debian

2014-11-19 Thread Emmanuel Bourg
Le 19/11/2014 14:55, Michael Meskes a écrit : > Also, as a bonus question to the Debian folks, should we try > establishing a cloudstack packaging group or do we push the effort into > the java packaging group? Cloudstack is more than welcome under the pkg-java umbrella if that helps you getting

RE: Cloudstack for Debian

2014-11-19 Thread Rayees Namathponnan
Hi Wido / Michael, I would like to be part of this group, have some RPM packaging experience in Cloudstack and Cloudplatform. Regards, Rayees -Original Message- From: Michael Meskes [mailto:mes...@debian.org] Sent: Wednesday, November 19, 2014 5:56 AM To: debian-devel@lists.debian.

Re: Cloudstack for Debian

2014-11-19 Thread Martin Zobel-Helas
Hi, On Wed Nov 19, 2014 at 14:55:51 +0100, Michael Meskes wrote: > Hi, > > Wido and I have been talking about bringing Cloudstack into Debian. > There is quite a bit of work involved because several dependencies are > not yet packaged. > > This obviously brings up the question if anyone else on