I can't speak to DEB, but a RPM is made by running a build script over a distribution. The script explains any prerequisites (in Karaf's case, just Java) where to put files, what permissions to use, what files are marked as to be deleted on uninstall, that kind of thing. Distribution varies, but there are a handful of large RPM repositories (mostly associated with different Linux distros) that we could target. They fulfill much the same role as Maven repos.
--- A. Soroka Software & Systems Engineering :: Online Library Environment the University of Virginia Library On Jan 15, 2013, at 12:14 PM, Andreas Pieber wrote: > What would we need to do to provide a RPM/DEB package? Where/how would > we need to distribute it? > > Kind regards, > Andreas > > On Tue, Jan 15, 2013 at 6:09 PM, [email protected] <[email protected]> > wrote: >> I have, for local consumption. I based the build on an ActiveMQ RPM script. >> It wasn't too difficult and I can send you the example, if you like. >> >> There has been discussion before on this list about maintaining a >> semi-"blessed" RPM of Karaf directly from the project. I'd be happy to work >> on that, if I could get guidance and help integrating it into the release >> process. >> >> --- >> A. Soroka >> Software & Systems Engineering :: Online Library Environment >> the University of Virginia Library >> >> On Jan 15, 2013, at 11:53 AM, Graham Leggett wrote: >> >>> Hi all, >>> >>> I am currently packaging an application stack as RPMs for deployment to a >>> production system, and am looking for RPM packages for karaf. >>> >>> JPackage provide a set of RPMs, but these RPMs depend on unstable (from >>> package's perspective) packages, and weigh in at an eye watering 274MB of >>> RPM dependencies. >>> >>> Has anyone other than package packaged karaf as an RPM? >>> >>> Regards, >>> Graham >>> -- >>> >>
