How to get well generated paths in a start script of a Debian package?

[greenled]

Hi. I recently built my first Debian package with Typesafe Activator
2.1.0, but it is not working as expected.
Once installed, my program is in /usr/share/Gloo-1.0 . The generated
Debian package creates a link to /usr/share/Gloo-1.0/bin/gloo in
/usr/bin/gloo. This way I can run "gloo" from everywhere because it is in
the path. But when I run "gloo" it doesn't find the main class
play.core.server.NettyServer .
I tried running "gloo -v" and then I saw that the start script was looking
for the jars in /usr/lib instead of /usr/share/Gloo-1.0/lib ¿why? I went
to the start script and in fact, it was looking for the jars in
"${app_home}/../lib" .
This works fine when I run the start script with
/usr/share/Gloo-1.0/bin/gloo, but it is not fun!! I should be able to run
the program just with "gloo", am I right?? So, could anybody tell me how
to make the generated start script sets the right path to libs?? By the
way, I am using Ubuntu 13.04 Raring Ringtail.

[muuki88]

This is a duplicate to #73 . Use the latest version of sbt-native-packager and everything will work fine.
Please read the last comments, too.

happy new year!

[jsuereth]

Also, what activator template did you use? We should bump the native
packager version in the template to avoid future confusion (cc @jamesward)

[jamesward]

Lets make sure we get the latest into Play 2.2.2.

[greenled]

I used the hello-play-framework template that comes with the Activator,
and I used the version 1.0.8 o the Activator. I think this issue is fixed
in the latest release of Activator, I will download it soon and try again.

El Mar, 31 de Diciembre de 2013, 3:54 pm, Josh Suereth escribió:

Also, what activator template did you use? We should bump the native
packager version in the template to avoid future confusion (cc @jamesward)

---

Reply to this email directly or view it on GitHub:
#115 (comment)
0

[muuki88]

I think we can close this. We'll already too late for play-2.2.2 @jamesward :(
We still need some testing for the rpm feature before we can ship a 0.7.0 release.