On 11/20/2014 07:50 PM, Marcus wrote: > For RPMs, the package.sh script that sets things up for rpmbuild could do > the mvn if we wanted to keep the RPM build process from downloading. > Something similar could be done from DEB, perhaps. >
Debian has helpers for that, so that hopefully smooths it out. > The dependencies thing though will be interesting to work out. It's a bit > unfortunate, IMO, because it reduces cross-platform compatibility and > compromises portability to have to target platform versions of libraries. > Inevitably we'll run into issues (as we have with libvirt jars, for > example). > I'm not convinced yet either. Although the way we do it right now isn't the best, it does work for us and our users. I'm afraid that we will run into a lot of deployment issues due to all the OS dependencies. Wido > On Wed, Nov 19, 2014 at 3:29 AM, Wido den Hollander <[email protected]> wrote: > >> I've sat down with some peope who are better in Debian packaging then I >> am and this is what we came up with: >> >> For Debian packages it is forbidden that during build it downloads >> external resources. Maven does this and that prevents CloudStack from >> ever going into the Debian repositories. >> >> We should not package all the JAR dependencies we have, but we should >> try to depend on packages available in Debian. >> >> Debian has a Wiki available for this: >> https://wiki.debian.org/Java/Packaging >> >> With some helpers we can make sure that Maven does not use external >> resources for dependencies, but uses locally available JAR files from >> the Debian repo. >> >> That is a thing which will take some serious time and we will run into >> problems there. Don't expect this to be done tomorrow. >> >> Our debian/rules file isn't really clean. They are going to look into >> this to make better use of debhelper. >> >> We might want to reach out to the packaging teams inside Debian to see >> if we can form a (small) team which can maintain the Debian packages for >> CloudStack. >> >> As a project we should watch for the RPM and DEB packages not drifting >> apart, since the user experience on both platforms should be equal. >> >> Wido >> >
