From: UnixOS2 Archive
To: "UnixOS2 Archive" <UnixOS2_Archive at unixos2.com>
Date: Wed, 19 Feb 2003 04:53:46 EST-10EDT,10,-1,0,7200,3,-1,0,7200,3600
Subject: [UnixOS2_Archive] No. 49

**************************************************
Tuesday 18 February 2003
 Number  49
**************************************************

Subjects for today
 
1  Re:  Is GREP the correct tool? : Maynard" <maynard.o at discourse.mentabolism.org>
2  Re:  ln : Hannes Hromadka <HromadkaJ at gmx.at>
3  Re:  ln : John Poltorak <jp at manninghammills.org>
4  Re:  TMPDIR : email at eracc.hypermart.net (ERACC Lists)
5   TMPDIR : John Poltorak <jp at manninghammills.org>
6   Is GREP the correct tool? : John Poltorak <jp at manninghammills.org>
7  Re:  ln : Hannes Hromadka <HromadkaJ at gmx.at>
8  Re:  TMPDIR : Holger Veit <holger.veit at ais.fhg.de>
9  Re:  ln : John Poltorak <jp at manninghammills.org>
10  Re:  CVS-20030219 : Ted Sikora <tsikora at ntplx.net>
11   Announcement: bash 2.05a : Jeff Robinson <jeffnik at anecho.mb.ca>
12   eCS file and directory standards : IanM" <IanM>

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

Date:  Wed, 19 Feb 2003 07:22:48 -0600 (CST)
From:  "Maynard" <maynard.o at discourse.mentabolism.org>
Subject:  Re:  Is GREP the correct tool?


# if grep localhost hosts; then echo ABC; else echo ZXY; fi
# 127.0.0.1     localhost
ABC
#


On Wed, 19 Feb 2003 11:41:09 +0000, John Poltorak wrote:

>
>If I simply want to test for the presence for a string in a file is GREP 
>the correct tool?
>
>If so, how do I use it in a shell script?
>
>eg:-
>
>if exist MY_STRING in MY_FILE then
> echo ABC
>else
> echo XYZ
>fi
>
>
>
>-- 
>John
>
>
>
>
>



**= Email   2 ==========================**

Date:  Wed, 19 Feb 2003 09:43:56 +0100
From:  Hannes Hromadka <HromadkaJ at gmx.at>
Subject:  Re:  ln

On Tue, Feb 18, 2003 at 06:30:17PM +0100, Holger Veit wrote:
> 
> Think further. Without the vision that such applications will then
> be also used, the whole porting enterprise is useless.

My problem with all these "just compiles and runs" ports, is that there
is no extensive testing.

One example:

I managed to compile slang using the build environement. Even a make
test worked fine and reported no errors. (needed only a few ifdefs)

Next I tried to build slrn with that slang libs and had a lot of
troubles. First I had mutliple defined entries in the libs. I could get
rid of that. Than I had unresolved externals, solved this too.

And finally I had a not working slrn port, because my slang did not know
how to handle the terminal.

But slang itself built fine and passed all test in make test. 8-(

 Greetings from Vienna
    
       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) <<<

**= Email   3 ==========================**

Date:  Wed, 19 Feb 2003 09:45:59 +0000
From:  John Poltorak <jp at manninghammills.org>
Subject:  Re:  ln

On Wed, Feb 19, 2003 at 09:43:56AM +0100, Hannes Hromadka wrote:
> On Tue, Feb 18, 2003 at 06:30:17PM +0100, Holger Veit wrote:
> > 
> > Think further. Without the vision that such applications will then
> > be also used, the whole porting enterprise is useless.
> 
> My problem with all these "just compiles and runs" ports, is that there
> is no extensive testing.

Yes, this is a very real problem, and something we need to address.
 
> One example:
> 
> I managed to compile slang using the build environement. Even a make
> test worked fine and reported no errors. (needed only a few ifdefs)
> 
> Next I tried to build slrn with that slang libs and had a lot of
> troubles. First I had mutliple defined entries in the libs. I could get
> rid of that. Than I had unresolved externals, solved this too.
> 
> And finally I had a not working slrn port, because my slang did not know
> how to handle the terminal.
> 
> But slang itself built fine and passed all test in make test. 8-(

The lesson here is that all the extra bits and pieces you needed to do 
ought to be added into the build process so that it is done automatically  
and any changes you make should be offered to the developer so that 
they can be incorporated into the original distributed release. This way 
your additional work only needs to be done on a one-off basis.

 
>  Greetings from Vienna
>     
>        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


**= Email   4 ==========================**

Date:  Wed, 19 Feb 2003 10:00:08 -0600
From:  email at eracc.hypermart.net (ERACC Lists)
Subject:  Re:  TMPDIR

 In: <20030219110957.F83 at manninghammills.org>
 On: Wed, 19 Feb 2003 11:09:57 +0000
 Screaming:  TMPDIR
 John Poltorak <jp at manninghammills.org> did rant:

+How common is it to have $TMPDIR defined on Unix system?

+Should we have it on UnixOS/2?

It is not defined on UnixWare nor OpenServer as a default when
logging on. Nor did I see it in any scripts I examined after reading
your message. I would imagine that most, if not all, modern unices
presume '/tmp' exists and is large enough to use if set up as a
separate file system. So, many scripts will just use '/tmp' for calls
to temporary storage.

That said, it is common for script writers to define default
directories and assign them to variables at the start of a script. So
the few scripts I looked over, less than 10, is not enough of a
sample to give you a definitive answer. Some install routines may
create and destroy subdirectories off '/tmp' so would use a variable
to hold the directory names. If *I* were to use a variable to hold
directions to '/tmp', etcetera I would use something shorter than
four characters, like $T, otherwise what is the point? ;-)

Gene <gene at eracc.hypermart.net>
-- 
+=========================-=>Unix & OS/2<=-=========================+
#   Owner and C.E.O. - ERA Computer Consulting - Jackson, TN USA    #
# eCS,OS/2,UnixWare,OpenServer & Linux Business Computing Solutions #
#     Please visit our www pages at http://eracc.hypermart.net/     #
+===================================================================+
               We run IBM OS/2 v.4.00, Revision 9.036                
 Sysinfo: 41 Processes, 159 Threads, uptime is 13d 14h 37m 58s 589ms 


**= Email   5 ==========================**

Date:  Wed, 19 Feb 2003 11:09:57 +0000
From:  John Poltorak <jp at manninghammills.org>
Subject:   TMPDIR

How common is it to have $TMPDIR defined on Unix system?

Should we have it on UnixOS/2?


-- 
John


**= Email   6 ==========================**

Date:  Wed, 19 Feb 2003 11:41:09 +0000
From:  John Poltorak <jp at manninghammills.org>
Subject:   Is GREP the correct tool?


If I simply want to test for the presence for a string in a file is GREP 
the correct tool?

If so, how do I use it in a shell script?

eg:-

if exist MY_STRING in MY_FILE then
 echo ABC
else
 echo XYZ
fi



-- 
John




**= Email   7 ==========================**

Date:  Wed, 19 Feb 2003 11:59:37 +0100
From:  Hannes Hromadka <HromadkaJ at gmx.at>
Subject:  Re:  ln

On Wed, Feb 19, 2003 at 09:45:59AM +0000, John Poltorak wrote:

> > My problem with all these "just compiles and runs" ports, is that there
> > is no extensive testing.
> 
> Yes, this is a very real problem, and something we need to address.
>  
> > But slang itself built fine and passed all test in make test. 8-(
> 
> The lesson here is that all the extra bits and pieces you needed to do 
> ought to be added into the build process so that it is done automatically  
> and any changes you make should be offered to the developer so that 
> they can be incorporated into the original distributed release. This way 
> your additional work only needs to be done on a one-off basis.

The problem here is, that I never succeeded to build slang by 
configure
make

After one lost day I fell back to use the working makefile.os2 from
the slang source tar ball.

Now I can build slrn again, also using the makefile.os2 from slrn.

Same for apache. Could not get it to build with configure, but the
makifle in the os2 port works fine.


    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) <<<

**= Email   8 ==========================**

Date:  Wed, 19 Feb 2003 13:34:24 +0100
From:  Holger Veit <holger.veit at ais.fhg.de>
Subject:  Re:  TMPDIR

On Wed, Feb 19, 2003 at 11:09:57AM +0000, John Poltorak wrote:
> How common is it to have $TMPDIR defined on Unix system?
> 
> Should we have it on UnixOS/2?

It is like TMP and TEMP an anachronism of certain Unixes
and certain Unix software that requires a location for
temporary files.

Historically, there are several approaches to this problem,
like tmpnam(), tmpname(), mktemp(), mkstemp(), mkdtemp()
and some more, and likewise, some programmers also figured 
that they should invent environment variables like the above
to make the location configurable. Actually, the presence
of any of these environment variables is an indication
that the software relying on it, is broken, poor designed
or otherwise lousy.

So, to summarize, whatever other Unixes use - lousy software
is a fact, so be prepared that you might need any of these
variables, as well as any of the api functions (whether or not
they are POSIX).

Holger

-- 
Please update your tables to my new e-mail address: 
holger.veit$ais.fhg.de  (replace the '$' with ' at '  -- spam-protection)


**= Email   9 ==========================**

Date:  Wed, 19 Feb 2003 14:23:59 +0000
From:  John Poltorak <jp at manninghammills.org>
Subject:  Re:  ln

On Wed, Feb 19, 2003 at 11:59:37AM +0100, Hannes Hromadka wrote:
> On Wed, Feb 19, 2003 at 09:45:59AM +0000, John Poltorak wrote:
> 
> > > My problem with all these "just compiles and runs" ports, is that there
> > > is no extensive testing.
> > 
> > Yes, this is a very real problem, and something we need to address.
> >  
> > > But slang itself built fine and passed all test in make test. 8-(
> > 
> > The lesson here is that all the extra bits and pieces you needed to do 
> > ought to be added into the build process so that it is done automatically  
> > and any changes you make should be offered to the developer so that 
> > they can be incorporated into the original distributed release. This way 
> > your additional work only needs to be done on a one-off basis.
> 
> The problem here is, that I never succeeded to build slang by 
> configure
> make

I have managed to build a libslang.a by this method, but it wasn't usable 
for creating any SLANG based apps.

 
> After one lost day I fell back to use the working makefile.os2 from
> the slang source tar ball.
> 
> Now I can build slrn again, also using the makefile.os2 from slrn.
> 
> Same for apache. Could not get it to build with configure, but the
> makifle in the os2 port works fine.


This is only partially correct. The Makefile is not only used for building 
apps, it is often used for installing them. At least those created through 
the configure & make process.

An OS/2 specific Makefile is fine as far as it goes, but ideally it 
wouldn't be necessary at all, and the configure script could be relied on, 
even on OS/2, to create a suitable Makefile.

I don't know if it is possible to incorporate the PC specific parts of the 
SLANG build into configure. Possibly not, but I do think it would be 
useful to be able to run 'Make install' and get everything installed 
automatically.

I'd also like to see a family mode version of mkmake included so that I 
wasn't reliant on DOS software... I did manage to build an OS/2 version
once but it was almost ten times as big as the DOS version. 
 
>     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



**= Email   10 ==========================**

Date:  Wed, 19 Feb 2003 22:18:30 -0500
From:  Ted Sikora <tsikora at ntplx.net>
Subject:  Re:  CVS-20030219

I can rename them and remove the earlier ones if you want?
Their in /os2/unix/devtools/cvs too.

Andrew Belov wrote:
> I'm uploading a refreshed build of CVS v 1.12.0.1 to the same location:
> 
> ftp://ftp.os2ports.com/incoming/cvs11202.zip
> (or is there a way to overwrite/move files?)
> 
> This one should have several RSH problems resolved, thanks to Christoph Schulte 
> Moenting for reporting them. Packaging has also been rectified.
> 
> The infamous "SSH -b" issue historically present in the EMX-new branch has now the 
> following resolution: we use "-b" only if no CVS_RSH was supplied. Then CVS runs 
> "rsh -b", and the IBM's RSH.EXE is meant to be located through PATH. Otherwise we 
> just invoke %CVS_RSH% without any intervening "-b" parameters.
> 

--
Ted Sikora
tsikora at ntplx.net



**= Email   11 ==========================**

Date:  Wed, 19 Feb 2003 23:05:51 -0600
From:  Jeff Robinson <jeffnik at anecho.mb.ca>
Subject:   Announcement: bash 2.05a

Hi folks,

Just leaving a notice that I've uploaded bash-2.05a to UnixOS2.org (I 
don't know if it has shown up in /incoming yet or not).

-----
bash (sh-compatible shell)



The GNU Bourne-Again SHell.  Bash is a sh-compatible command interpreter 
that executes commands read from the standard input or from a file. 
Bash also incorporates useful features from the Korn and C shells (ksh 
and csh).  Bash is ultimately intended to be a conformant implementation 
of the IEEE Posix Shell and Tools specification (IEEE Working Group 1003.2).

----

This port contains many fixes original done by Jun SAWATAISHI plus an 
additional TMPDIR fix.  (Previously temp files were written to the 
current working directory, creating quite the mess).

Jeff
-- 
----------------
Whatza JamochaMUD?
http://jamochamud.anecho.mb.ca

Or other stuff: http://www.anecho.mb.ca/~jeffnik
  -----------------------------------------------------------

  

**= Email   12 ==========================**

Date:  Wed, 19 Feb 2003 23:49:01 +1100 (EDT)
From:  "IanM" <IanM>
Subject:   eCS file and directory standards

>From:     Nick Morrow
>email:     morrown at fibertel.com.ar
>
>Comments: -
>Greetings,
>
>Glenn Hudson and I were exchanging emails the other day and he
> mentioned to me that he was talking to someone in this group who
> had some good ideas concerning eCS.  I participate in the
> eCSDevGroup and more or less act as the secretary.  One of the
> documents I've been working on is called eFDS-1.TXT which outlines
> file and directory standards which are starting to be used in eCS.  We
> have borrowed from Unix standards somewhat but would like to confirm
> with folks in this group so as to get your inputs.
>
>Regards,
>
>Nick

Cheers
IanM
http://www.os2site.com/

Student excuse of the 90's: "Windows ate my homework."