At the moment, it might be easiest to explain what the root problem is and give you a way to work around it.
First, this problem is only with RPM builds and does not occur in DEB builds. The reason for this is that the DEB builds are done under the "fakeroot" environment and that environment provides the correct default prefix. RPM builds are done under a standard userid and the prefix that get set for a standard user is /usr/local and not /usr. This is a big problem because /usr/local/bin is NOT in the default PATH for most RPM-based distributions. To correct this we supply our own --prefix option when building an RPM which is set to /usr. We could use fakeroot for the RPM builds but it is not installed by default on any distribution due to it being a security risk. So how do you work around this? Look at line 145 of the ./platform/unix/oorexx.spec.in file. There you will see where we override the prefix during the building of the RPM. Simply remove this option from the configure command and rebuild your RPM by rerunning the configure command with your own prefix and then doing the make rpm command. That will build an RPM with your custom prefix. You might think that we could install the fakeroot command onto the distribution and set a prereq on it and we would be done with this problem. But no, that will not work. If the RPM is then built as the root user the fakeroot command gives errors and the build will fail. That is why we have our workaround. I may do some experimenting this week with testing to see if we are the root user and then supplying the correct build options. I will let you know how this turns out. David Ashley On Sat, 2013-04-06 at 22:58 -0400, Michael Lueck wrote: > Greetings, > > It has been some time since I brought the topic up last. For Linux shared > hosting, we are stuck running ooRexx 3.2 as the highest version. On shared > hosting, we do not have a root account to the > server. Installed software requires the build process to support the prefix > switch and to be compiled based on the home directory as the deployment > target. > > Has there been any progress made at researching if by some creative work that > restriction could be lifted again? I would very much like to maintain the > latest ooRexx version across hosts, including > shared hosting. > > Sincerely, > ------------------------------------------------------------------------------ Precog is a next-generation analytics platform capable of advanced analytics on semi-structured data. The platform includes APIs for building apps and a phenomenal toolset for data science. Developers can use our toolset for easy data analysis & visualization. Get a free account! http://www2.precog.com/precogplatform/slashdotnewsletter _______________________________________________ Oorexx-devel mailing list Oorexx-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/oorexx-devel
