[
https://issues.apache.org/jira/browse/PIO-22?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15426974#comment-15426974
]
Pat Ferrel commented on PIO-22:
-------------------------------
What if we rename this script "source-install.sh" and have "install.sh" too?
They would both be moved to the docs repo and referenced in docs as "install
last stable" or "install latest source"?
Alternatively we can just have the "install.sh" do a source build but from the
master branch.
That way, you can always install the snapshot AND the releases without getting
the 2 confused?
I mention moving out of the repo only because if you download source then run
it from bin/, won't it mess us the existing download or at least use a
different source. Wouldn't that would be confusing? So many people mess this up
in the wild.
[~emergentorder], [~dszeto]?
> 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)
