[
https://issues.apache.org/jira/browse/PIO-22?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15431309#comment-15431309
]
Pat Ferrel commented on PIO-22:
-------------------------------
To get this resolved I suggest we release with the build-from-source version of
install.sh and point to it from the docs site.
We can change this later to a install from binaries if we want.
The install.sh in the develop branch gets
https://codeload.github.com/apache/incubator-predictionio/tar.gz/develop so at
merge with master time we just need to change it to point to /master leaving
the one in develop as-is
if so we can resolve this and put it on the release checklist.
> Install.sh issues
> -----------------
>
> Key: PIO-22
> URL: https://issues.apache.org/jira/browse/PIO-22
> Project: PredictionIO
> Issue Type: Task
> Affects Versions: 0.10.0
> Reporter: Pat Ferrel
> Fix For: 0.10.0
>
>
> The install.sh pushed with the AML merge has been re-worked to do a local
> build of pio in all cases. This will work even for snapshots as long as there
> is a tar.gz to download whereas the older method only worked on releases.
> Not sure if we want to force source builds for releases so bringing this up
> for discussion.
> For one thing is would require a downloadable package, where we also could
> use git and avoid the packaging of a source tar. For another we'd probably
> like a non-source build version too.
> Going back to a reversion is not ideal since the old install.sh misses
> several important cases like installing postgres with es for templates like
> the UR, which expect es.
> Can anyone pick this up or comment?
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
