3 ms·
I downloaded the OSX .pkg installer and didn't see anything in /Applications or /opt after running it and telling it to install to my root drive. Just glancing
by res0nat0r 11y ago
I downloaded the OSX .pkg installer and didn't see anything in /Applications or /opt after running it and telling it to install to my root drive. Just glancing at some docs on your site I see pipeline-init, so doing a find on / to find out where it placed the binaries see it installed to:
/usr/lib/pipelinedb/usr/lib/pipelinedb/bin/pipeline-init
Is this intentional?
EDIT:
After playing around with the .pkg file it looks like the packed Payload contains '/usr/bin/pipelinedb/usr/lib/pipelinedb' which is probably the problem. I see broken symlinks for pipeline-init etc in /usr/bin pointing to /usr/lib/pipelinedb, so I'm guessing this repetition of the path above is a mistake.
Also I see a postinstall script creating a symlink from pipeline to psql. This seems like a bad idea as psql is pretty universal already as the name for the PostgreSQL CLI binary, maybe 'pipesql' might be better?
- grammr 11y agoSorry about that, OSX packaging is a bit finicky right now. We'll publish a package with more sensible defaults very shortly.
- kawera 11y agoHomebrew would be nice too.
- res0nat0r 11y agoGreat thanks! Looking forward to checking it out.
- grammr 11y agoWe just updated http://www.pipelinedb.com/download/0.7.7/osx http://www.pipelinedb.com/download/0.7.7/osx. Please shoot me an email (I'm Derek) if you have any issues installing this package. Thanks for your patience!
- cuttinedg 11y agoThere was an error with init and created an issue in github https://github.com/pipelinedb/pipelinedb/issues/1025 https://github.com/pipelinedb/pipelinedb/issues/1025
- mfenniak 11y agoA Homebrew (http://brew.sh/ http://brew.sh/) package might be a better approach that a .pkg. It's easier to maintain for you, and, definitely easier for a user. Not all OSX users use Homebrew, of course, but I think many in your audience would.