|
From: | Juergen Sauermann |
Subject: | Re: [Bug-apl] Package Manager installation issues and proposal - feedback requested |
Date: | Thu, 05 Jun 2014 15:43:57 +0200 |
User-agent: | Mozilla/5.0 (X11; Linux i686; rv:17.0) Gecko/20130330 Thunderbird/17.0.5 |
Hi David,
I am planning to generate the preferences file with ./configure so that the libdirs for GNU APL in the default preferences file (in /etc/gnu-apl.d or in /usr/local/etc/gnu-apl.d depending on the nature of the target system) points to typically /usr/lib/apl or to /usr/local/lib/apl. Somehow ./configure decides if eg /usr/lib or /usr/local/lib is used; this can be changed with prefix= in ./configure. The bottom line is that the default values in the preferences file will be (on a /usr/lib kind of system): /usr/lib/apl/wslib3 for library reference 3 /usr/lib/apl/wslib4 for library reference 4 /usr/lib/apl/wslib5 for library reference 5 library references 0, 1, and 2 will have no default values, even though I was thinking of defaulting library reference 0 to $HOME/workspaces (and maybe 1 to $GROUP/wslib1). This is to not override user libraries by the installation. make install is normally executed by root so no file is safe and it is important to keep files of the user separate from files installed by GNU APL. In GNU APL itself there is a )LIBS command that shows the absolute paths for the library references. It your case the package manager should go to /usr/lib/apl/wslib3 if it is completely ISO-compatible or into /usr/lib/apl/wslib5 if it uses GNU APL features. If your package only contains executable file (eg APL workspaces) and has no need for compilation then an autoconf file would be fairly straightforward and could take care of the installation issues. It would also make sure that the files of the package use the same conventions (eg usr/lib vs. /usr/local/lib), which is very important for different libraries to find each other. /// Jürgen On 06/04/2014 08:03 PM, David Lamkins wrote:
|
[Prev in Thread] | Current Thread | [Next in Thread] |