[
https://issues.apache.org/jira/browse/PIO-22?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15843147#comment-15843147
]
Alexander Merritt commented on PIO-22:
---------------------------------------
Agree. As discussed, this currently pulls from develop and does a build from
source & install. As Pat mentioned if we just switch to master, it will provide
the latest release. If you want to build from develop, then swap in the source
manually, you can, but this way you get most recent release. Obviously this
will take a little longer on the user end due to the compile, but the end
result is the same pointing to a binary. In fact, providing the source and
build yourself is a bit more ASF-ish (even if not required here). We can open a
new ticket if someone really wants a binary here.
> 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-incubating
> Reporter: Pat Ferrel
> Fix For: 0.11.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)
