Then I think we are on the same path. I headed down the second option,
symlinks into system subdirectories.
Bruce
On Feb 9, 2011, at 2:10 PM, David Ashley wrote:
> Not that I can think of. Just be aware that our roadmap is to place
> everything
> in system subdirectories where that makes sens
Not that I can think of. Just be aware that our roadmap is to place everything
in system subdirectories where that makes sense. Or at least place symlinks in
the system subdirectories.
David Ashley
On 02/09/2011 03:58 PM, CVBruce wrote:
> If you are putting the programs into /usr/bin, then the
If you are putting the programs into /usr/bin, then the corresponding place to
put the libraries would be /usr/lib. It would be inconsistent, in my mind to
add /usr/lib/ooRexx to the system path.
I just changed my copy of configure.ac to move ooRexx back to /opt/ooRexx, for
Mac OS X only.
I d
I will put my 2 cents in here :-)
mark is correct that we initially thought we could get away without symlinks
for
the ooRexx libraries in 4.1.0. It turned out not to be the case for a number of
reasons. So now we need to correct our error.
There are two possibilities.
1. Move the libraries t
On Wed, Feb 9, 2011 at 11:51 AM, CVBruce wrote:
> As you may have seen, I now have ooRexx 4.1.0 compiling on x86_64, i386, and
> ppc. So I will resume working on install packages and disk images.
Great.
> I don't feel that my make file skills are up to creating a target to build
> the mac os
I agree that is the direction, and I've been making haste slowly towards that.
The scripts exist to make an install package for 4.0.1, but I wasn't aware of
the location changes for 4.1.0 and I have to go back and rework the scripts.
If the consensus is that I can put the files in any location
On Wed, Feb 9, 2011 at 2:08 PM, Mark Miesfeld wrote:
> On Wed, Feb 9, 2011 at 10:36 AM, CVBruce wrote:
>
>> Ok, so the behavior I'm seeing is somewhat standard? Does this mean that
>> the libraries are going to stay where they are, or are they going back to
>> /opt/ooRexx/lib/ooRexx?
>
> Well,
On Wed, Feb 9, 2011 at 10:36 AM, CVBruce wrote:
> Ok, so the behavior I'm seeing is somewhat standard? Does this mean that the
> libraries are going to stay where they are, or are they going back to
> /opt/ooRexx/lib/ooRexx?
Well, they're going to stay there until one of the developers decide
Ok, so the behavior I'm seeing is somewhat standard? Does this mean that the
libraries are going to stay where they are, or are they going back to
/opt/ooRexx/lib/ooRexx?
Thanks,
Bruce
On Feb 9, 2011, at 10:28 AM, Mark Miesfeld wrote:
> On Wed, Feb 9, 2011 at 10:18 AM, CVBruce wrote:
>
>> I
On Wed, Feb 9, 2011 at 10:18 AM, CVBruce wrote:
> I had to add a path to the ooRexx (4.1.0) libraries in /usr/lib/ooRexx. In
> other *nix systems are these picked up automatically or do you have to add a
> path to them?
>
> In 4.0.1, I symlinked the libraries from /opt/ooRexx/lib/ooRexx/ to /u
Hi,
I had to add a path to the ooRexx (4.1.0) libraries in /usr/lib/ooRexx. In
other *nix systems are these picked up automatically or do you have to add a
path to them?
In 4.0.1, I symlinked the libraries from /opt/ooRexx/lib/ooRexx/ to /usr/lib,
and I didn't require a specific path to them.
11 matches
Mail list logo
