You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@kudu.apache.org by "Alex Rodoni (JIRA)" <ji...@apache.org> on 2018/12/10 20:57:00 UTC
[jira] [Commented] (KUDU-1344) Make it easier to install Kudu from
source
[ https://issues.apache.org/jira/browse/KUDU-1344?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16715547#comment-16715547 ]
Alex Rodoni commented on KUDU-1344:
-----------------------------------
From: Adar
1. Users should copy out the `kudu-tserver`, `kudu-master`, and `kudu` binaries from within the `bin` subdirectory of their Kudu build directory.
2. We typically recommend putting `kudu` in the user's bin directory (e.g. `/usr/bin`) and the server binaries in the sbin directory (e.g. `/usr/sbin`)
3. By default, `make install` will install things into `/usr/local` rather than `/usr`. So the above example locations will actually be `/usr/local/bin` and `/usr/local/sbin`. Not sure which you'd prefer to document, or whether you think this detail is worth documenting either (edited)
> Make it easier to install Kudu from source
> ------------------------------------------
>
> Key: KUDU-1344
> URL: https://issues.apache.org/jira/browse/KUDU-1344
> Project: Kudu
> Issue Type: Bug
> Components: build
> Affects Versions: 0.7.0
> Reporter: Adar Dembo
> Priority: Major
>
> At the moment, the best resource we have for getting Kudu from raw source code to "up and running" is the documentation that describes how to build it. Some gaps:
> # Docs that explain how to "install" it (i.e. where to copy the binaries, how to integrate into init.d/systemd, where to place configuration files, etc.)
> # A "make install" target that doesn't just install C++ client files but instead captures the above too.
> # Init.d scripts and basic configuration files so people don't have to write their own.
> # Packaging code so it'd be possible to build system packages from source code (i.e. "soup to nuts"), perhaps using [fpm|https://github.com/jordansissel/fpm].
> Step 3 can be provided by opening up more of the internal Cloudera packaging infrastructure for Kudu. Step 4 may obviate the need for said infrastructure altogether, which isn't a bad idea because it's inscrutable, complicated and very error-prone.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)