Re: 7Zip Problem

Dennis Lovelady wrote:

Golly, jeepers, Scott! Usually this stuff is under /etc and we're not
talking about that at all.

The Unix systems I work in put their config files in /usr/local/etc for packages that don't come with the OS, and in /etc for stuff that does come with the OS.

I have yet to see a package that looks under
/usr/local for its configuration files (it may look in its own directory or
in a subdir of same, but that's not the same thing).

Good grief, do I have to spell everything out for you?! Most Unix software is configured using something called a "prefix" at compile time. So you do something like this

./configure --prefix=/usr/local

and that means it'll expect binaries in /usr/local/bin, libraries in /usr/local/lib, configuration in /usr/local/etc, and so on... The point is, it looks under /usr/local/SOMETHING instead of /QOpenSys/usr/local/SOMETHING.

And PLEASE don't reply saying "I've never seen a package that uses the name 'SOMETHING'" I don't mean SOMETHING literally... I'm just not going to try to list every single subdirectory that can be within /usr/local.

The ./configure script causes that pathname (/usr/local/SOMETHING) to be placed in various macros in a C source file, causing it to be compiled into the program. Since the software was compiled on an actual AIX box, and not something I compiled myself, I can't change that pathname.

Using chroot at install-time won't help with this. I could use it at runtime to solve the problem, but then I wouldn't be able to access other file systems.

Sorry if this doesn't convince you. Honestly, I don't care anymore if it does or not. That's been my experience, and I'm solving the problem with the symbolic link.

If you don't like it, use someone else's software. Or donate the time to fix the problem. Frankly, unless you're willing to put in the time and effort to solve these problems for the community, PLEASE don't sit and complain about the way I do things.