Josh Saddler - Latest comments on in the works

In response to: in the works

Josh Saddler [Member] — Sat, 25 Nov 2006 10:54:43 +0000

@Stuart:

Thanks for the tip; I'll check out the NX stuff. Wrapper scripts seem like more of a pain than any other solution, but I'll investigate everything I come across.

In this case though, since it is a purely binary distribution, it should be placed in /opt/. This greatly simplifies things for both x86 and amd64; no need to specify installdirs based on arch.

And it works fine, just fine, especially if I drop the proper stuff in /opt and call it with LD_LIBRARY_PATH="/opt/foo" command.sh; it properly picks up the stuff. Actually, regarding /usr/appname, the weird thing is that in the RPM, it specifies files in /usr/bin/, /usr/share/, /usr/lib/, and /usr/appname/. The executables are located in both /usr/bin/ and /usr/appname/. It's seriously messed up; should just be /usr/lib/ and /usr/bin/, with the license/documentation in /usr/share/. That is, if it behaved properly. It needs to all go in /opt/ anyway.

Regarding the secrecy, well...maybe I just want to be the first one to offer it to the community. As soon as I can figure out a solution to the env/library loading/installdir issue, then I'll open a bug for it and provide some installation docs on my devspace. :)

Because if none of this works out, then I don't want too many folks besides myself to have wasted their time on it. I figure that at the least, the time I spend learning about Portage and ebuilds and how to work around more complicated installation issues is time well spent, even if this particular project ends up failing.

In response to: in the works

Stuart Herbert [Visitor] — Sat, 25 Nov 2006 10:31:34 +0000

LDPATH in /etc/env.d isn't always the right way to go. A wrapper script is sometimes the easier option. See any of the NX packages for an example of how that approach works.

Don't consider the devmanual as the definitive word on where things go. That simply isn't true. Sometimes, the right thing to do is to put stuff where upstream expects it. Users switching to Gentoo from other platforms appreciate it - because the app is where they expect it.

I don't know the app (what's with all the secrecy? That's not the Gentoo way!), but if it was me, I'd be most likely to get it working in /usr/<appname> first, before even considering moving it to /opt. It's easier to move something that works than to try and get something working in the first place.

Best regards,
Stu

In response to: in the works

Josh Saddler [Member] — Sat, 25 Nov 2006 10:03:34 +0000

@dberkholz:
ahh, thanks Donnie. now i have to learn more about how i can actually make it work with said LDPATH. :p

yay for #gentoo-dev-help! and, of course, our wonderful devmanual. :)

In response to: in the works

Donnie Berkholz [Visitor] — Sat, 25 Nov 2006 08:03:28 +0000

LDPATH in /etc/env.d/ file.