It works well for me. Perhaps the biggest thing that it doesn't do
for me is to get the rxapid script into an appropriate place so that
it gets started. On the other hand once the script is in place, I
don't see it changing all that often.
Bruce
On Aug 11, 2010, at 8:07 AM, David Ashley wro
All good points Mark. Although as you can see, I'm finding it easier
to install from source than to build a #...@*!@ installer package.
Bruce
On Aug 11, 2010, at 7:47 AM, Mark Miesfeld wrote:
> On Wed, Aug 11, 2010 at 7:32 AM, CVBruce wrote:
>> ...
>> There are really two situations where a
Mark is correct. make install should only be used by a developer. To be
honest
though, I am not sure that it even works for the ooRexx build as I never use it.
David Ashley
On 08/11/2010 09:47 AM, Mark Miesfeld wrote:
> On Wed, Aug 11, 2010 at 7:32 AM, CVBruce wrote:
>> ...
>> There are real
On Wed, Aug 11, 2010 at 7:32 AM, CVBruce wrote:
> ...
> There are really two situations where a post install
> script gets executed, when installing from source and when installing
> from an installer package. It would be best if one script did both.
>
> So after I tailor the file during make ins
You're right Mark. I guess I was being paranoid last night when I
wrote this. It's not like I'm setting the the set UID or GID bits in
the permissions. There are really two situations where a post install
script gets executed, when installing from source and when installing
from an insta
On Tue, Aug 10, 2010 at 8:48 PM, CVBruce wrote:
> As part of the Mac OS X install I have to create a shell script to put
> the symbolic links into /usr/bin etc.
>
> The installer executes the script after the install. The script has
> version, release and mod numbers in it.
This is essentially