[
https://issues.apache.org/jira/browse/PIO-22?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15425209#comment-15425209
]
Alexander Merritt commented on PIO-22:
---------------------------------------
Currently there are a couple of bugs. One is fixed by a user PR on Github, the
other (new install options broken) I've fixed and will push under this JIRA.
Also removed the user email submit, which I believe was discussed elsewhere.
Leaving it to build from develop for now, as we don't have a release tar yet to
point it to. After the 0.10.0 release, I propose the install.sh return to
pointing to releases, and changes to it should be considered not bound to the
release cycle (like the doc).
> 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)
