Date: Mon, 7 Apr 2003 02:40:40 EST-10EDT,10,-1,0,7200,3,-1,0,7200,3600
Subject: [Ux2bs_Archive] No. 127

**************************************************
Sunday 06 April 2003
 Number  127
**************************************************

Subjects for today
 
1  Re:  New Apache : Hannes Hromadka <HromadkaJ at gmx.at>
2  Re:  New Apache : John Poltorak <jp at warpix.org>
3  Re:  Suggested changes to build.sh : sma at sohnen-moe.com
4  Re:  Suggested changes to build.sh : sma at sohnen-moe.com
5  Re:  Suggested changes to build.sh : John Poltorak <jp at warpix.org>

**= Email   1 ==========================**

Date:  Mon, 7 Apr 2003 10:41:00 +0200
From:  Hannes Hromadka <HromadkaJ at gmx.at>
Subject:  Re:  New Apache

On Sun, Apr 06, 2003 at 10:46:30AM +0100, John Poltorak wrote:
> 
> Can someone try building this? It shouldn't be too difficult since a 
> binary package for OS/2 is available.

Is there a binary version of a sh.exe available where test -x works ?


    Ciao,  Hannes

-- 
Johannes Hromadka     | Email Office: HromadkaJ at gmx.at
                      |       Home  : Johannes.Hromadka at gmx.net
Vienna/Austria/Europe | OECC: http://www.oecc.org/
>>> Rust never sleeps   (borrowed from Neil YOUNG) <<<
_______________________________________________
UX2BS mailing list
UX2BS at os2ports.com
http://os2ports.com/mailman/listinfo/ux2bs
**= Email   2 ==========================**

Date:  Mon, 7 Apr 2003 11:42:13 +0100
From:  John Poltorak <jp at warpix.org>
Subject:  Re:  New Apache

On Mon, Apr 07, 2003 at 10:41:00AM +0200, Hannes Hromadka wrote:
> On Sun, Apr 06, 2003 at 10:46:30AM +0100, John Poltorak wrote:
> > 
> > Can someone try building this? It shouldn't be too difficult since a 
> > binary package for OS/2 is available.
> 
> Is there a binary version of a sh.exe available where test -x works ?


You could try building PDKSH using the latest diff I have...

If you do an RSYNC refresh of UX2BS from 213.152.37.92 you should pick up 
pdksh-5.2.14.diff.


I'd be interested to know whether the patch works correctly...
 
> 
>     Ciao,  Hannes
> 
> -- 
> Johannes Hromadka     | Email Office: HromadkaJ at gmx.at
>                       |       Home  : Johannes.Hromadka at gmx.net
> Vienna/Austria/Europe | OECC: http://www.oecc.org/
> >>> Rust never sleeps   (borrowed from Neil YOUNG) <<<


-- 
John



_______________________________________________
UX2BS mailing list
UX2BS at os2ports.com
http://os2ports.com/mailman/listinfo/ux2bs
**= Email   3 ==========================**

Date:  Mon, 07 Apr 2003 12:08:29 -0700
From:  sma at sohnen-moe.com
Subject:  Re:  Suggested changes to build.sh

>
>Could you have a look at the latest version?
>
  So you added two checks:
1. Verifying the package is in build.table
2. Adding posix2 to the paths.

  They look good to me.
  I made a (unsuccessful) attempt to prevent adding posix2 if it is
already in the paths but could find no way to do that. grep returned
success regardless of the presence (or not) of posix:

if [ `echo $PATH | grep -iqF 'posix'` ]; then ...

  Another thing that is good to add is setlocal and endlocal in
build.cmd. This prevents changes to the environment from becoming
permanent.


_______________________________________________
UX2BS mailing list
UX2BS at os2ports.com
http://os2ports.com/mailman/listinfo/ux2bs
**= Email   4 ==========================**

Date:  Mon, 07 Apr 2003 13:39:01 -0700
From:  sma at sohnen-moe.com
Subject:  Re:  Suggested changes to build.sh


>The default setting is to have Posix/2 in the environment, however
>there  are occasions when Posix/2 simply doesn't work, so I've provided
>a  mechanism for ignoring Posix/2 for particular apps. This is done by 
>adding the app to p2_exc.lst.
>
  Yes, I later realized this. I seem to be dyslexic about boolean things
<sigh>.

>>   Another thing that is good to add is setlocal and endlocal in
>> build.cmd. This prevents changes to the environment from becoming
>> permanent.
>
>The environment set by build.cmd only exists for the duration of that 
>session. I don't really understand what problems it causes.
>
  I recall having problems with the environment changing if
setlocal/endlocal were not used in other situations (non-ux2bs). Maybe
it just a peculiar thing I was doing.


_______________________________________________
UX2BS mailing list
UX2BS at os2ports.com
http://os2ports.com/mailman/listinfo/ux2bs
**= Email   5 ==========================**

Date:  Mon, 7 Apr 2003 20:43:59 +0100
From:  John Poltorak <jp at warpix.org>
Subject:  Re:  Suggested changes to build.sh

On Mon, Apr 07, 2003 at 12:08:29PM -0700, sma at sohnen-moe.com wrote:
> >
> >Could you have a look at the latest version?
> >
>   So you added two checks:
> 1. Verifying the package is in build.table
> 2. Adding posix2 to the paths.
> 
>   They look good to me.

There is also a check to ensure that an app has been successfully 
extracted. If it hasn't there is an early exit.

>   I made a (unsuccessful) attempt to prevent adding posix2 if it is
> already in the paths but could find no way to do that. 

The default setting is to have Posix/2 in the environment, however there 
are occasions when Posix/2 simply doesn't work, so I've provided a 
mechanism for ignoring Posix/2 for particular apps. This is done by 
adding the app to p2_exc.lst.

>   Another thing that is good to add is setlocal and endlocal in
> build.cmd. This prevents changes to the environment from becoming
> permanent.


The environment set by build.cmd only exists for the duration of that 
session. I don't really understand what problems it causes.

Personally, when I'm building any app I run:-


start /f build APPNAME from File Commander.

When the build finishes it offers an opportunity to run other commands 
in the correct environment which may be pertinant to the build just 
attempted. Sometimes it fails, but just running 'Make' in this session 
will work. 


-- 
John


_______________________________________________
UX2BS mailing list
UX2BS at os2ports.com
http://os2ports.com/mailman/listinfo/ux2bs