Comment 5 for bug 586459

My apologies in advance if you find this hard to follow, but I will try to explain the process...

The fundamental issue seems to be that I'm not trying to install nathive on my machine, but create an Archlinux package for others to install. To do this, I essentially need to install nathive to a ../nathive/pkg/ directory. The package manager then creates a tarball of what ends up in this /pkg directory, and these exact files eventually make it to another user's machine. So, for example, the ../nathive/pkg/usr/bin/nathive file that I create ultimately becomes the /usr/bin/nathive file on the machine of someone that installs nathive.

In order to accomplish this, I have to replace the hardcoded BASE path in the nathive makefile with a path that points to ../nathive/pkg/. That installs nathive to the location needed by the package manager. However, this causes the ../nathive/pkg/usr/bin/nathive to be pointing to the nathive python file in ../nathive/pkg/. This means that ultimately when the user installs the program, they get a file /usr/bin/nathive that points to the nathive python file in ../nathive/pkg/ as well, which doesn't exist. So after I install nathive to ../nathive/pkg/, I modify the ../nathive/pkg/usr/bin/nathive file to point to the appropriate location. This means that the user who installs nathive has a /usr/bin/nathive file pointing to the appropriate location as well.

It sounds like the META file is the missing piece here. I can edit this as well, but as you are hopefully seeing, there is getting to be a lot of manual work on my end to make this all work correctly.

I am at work right now, but will attach the requested files when I get home.