An alternative to producing packages is a tool like fpm <https://github.com/jordansissel/fpm>.
-- Philip On Wed, Oct 11, 2017 at 9:00 AM, Michael Brown <[email protected]> wrote: > Hi sky, > > Unfortunately we don't provide this upstream yet (contributions welcome!), > but the summary is that you would craft a specfile. In the specfile, you > would > > 1. Define package dependencies. bin/bootstrap_development.sh in Impala > source is a good way to know what dependencies Impala has. > > 2. Define how to build Impala. (buildall.sh in Impala source) > > 3. Define what artifacts from buildall.sh you want to put in your package > (look in be/build) and where they should reside when a user installs your > RPM (e.g., /opt/impala/bin/impalad) > > 4. You would have to create and bundle more items yourself, like initd or > systemd startup files and any conf files > > http://rpm.org/documentation.html seems like a good start for a reference. > > Good luck! > > > On Wed, Oct 11, 2017 at 4:15 AM, sky <[email protected]> wrote: > > > Hi all, > > How to compile impala into rpm package？ >
