Date: Tue, 2 Dec 2003 14:17:27 EST-10EDT,10,-1,0,7200,3,-1,0,7200,3600 Subject: [UnixOS2_Archive] No. 258 ************************************************** Monday 01 December 2003 Number 258 ************************************************** Subjects for today 1 Re: make DIRSETGID=: install : T.Sikora" 2 Re: make DIRSETGID=: install : T.Sikora" 3 Re: Python install : Andrew MacIntyre 4 Re: Python install : John Poltorak 5 Re: UnixOS/2 distro : Michael Zolk 6 make DIRSETGID=: install : John Poltorak **= Email 1 ==========================** Date: Tue, 02 Dec 2003 19:33:15 -0500 From: "T.Sikora" Subject: Re: make DIRSETGID=: install John Poltorak wrote: > Can anyone explain what this means:- ? > > make DIRSETGID=: install > > To install without turning on the setgid bit on directories. -- T.Sikora tsikora at ntplx dot net **= Email 2 ==========================** Date: Tue, 02 Dec 2003 19:40:20 -0500 From: "T.Sikora" Subject: Re: make DIRSETGID=: install T.Sikora wrote: > John Poltorak wrote: > >> Can anyone explain what this means:- ? >> >> make DIRSETGID=: install >> >> > > To install without turning on the setgid bit on directories. > It fails otherwise with just make install. The cgi programs don't get installed. -- T.Sikora tsikora at ntplx dot net **= Email 3 ==========================** Date: Tue, 2 Dec 2003 21:07:47 +1100 (EST) From: Andrew MacIntyre Subject: Re: Python install On Mon, 1 Dec 2003, John Poltorak wrote: > When building Python from source, what is the correct installation > procedure? If you have a copy of my binary package, you want all the files that it contains in an appropriate directory structure. I'm guessing that you want: - *.exe in /usr/local/bin - python23.dll /usr/local/[bin|dll|lib] - the remainder of the binary package should be replicated in /usr/local/python2.3, and (if set) $PYTHONHOME=/usr/local/lib/python2.3 I hope to do some more work on this over Christmas, including trying to move the optional package building out of the makefile into a setup.py script (al la the normal Unix build). Unfortunately, the standard setup.py needs a lot of changes to its library detection logic to work with a vanilla EMX environment and its unlikely the changes would be accepted as they're so intrusive, so an EMX specific setup.py has to be the way to go for my purposes. It is probable that if you can get the UX2 build setup close to that of Cygwin, the standard setup.py will work for you. In particular, the standard setup.py script looks for libraries using the "lib.[a|so]" naming pattern rather than the ".a" standard with EMX. Because Python uses -Zomf to build extensions (which are DLLs), you need OMF versions of the libraries too. -- Andrew I MacIntyre "These thoughts are mine alone..." E-mail: andymac at bullseye.apana.org.au (pref) | Snail: PO Box 370 andymac at pcug.org.au (alt) | Belconnen ACT 2616 Web: http://www.andymac.org/ | Australia **= Email 4 ==========================** Date: Tue, 2 Dec 2003 21:38:44 +0000 From: John Poltorak Subject: Re: Python install On Tue, Dec 02, 2003 at 09:07:47PM +1100, Andrew MacIntyre wrote: > On Mon, 1 Dec 2003, John Poltorak wrote: > > > When building Python from source, what is the correct installation > > procedure? > > If you have a copy of my binary package, you want all the files that it > contains in an appropriate directory structure. Do you have a handy script which will put all the files from the built distribution archive into the directory structure you use? > I'm guessing that you want: > - *.exe in /usr/local/bin > - python23.dll /usr/local/[bin|dll|lib] > - the remainder of the binary package should be replicated in > /usr/local/python2.3, and (if set) $PYTHONHOME=/usr/local/lib/python2.3 That sounds about right although I never know if /usr/lib/python should be used instead... Does the LIB_DIR defined in Makefile get used anywhere? > I hope to do some more work on this over Christmas, including trying to > move the optional package building out of the makefile into a setup.py > script (al la the normal Unix build). > > Unfortunately, the standard setup.py needs a lot of changes to its library > detection logic to work with a vanilla EMX environment and its unlikely > the changes would be accepted as they're so intrusive, so an EMX specific > setup.py has to be the way to go for my purposes. > > It is probable that if you can get the UX2 build setup close to that of > Cygwin, the standard setup.py will work for you. Does anyone know if we should try to emulate Cygwin as far as installation goes? > -- > Andrew I MacIntyre "These thoughts are mine alone..." > E-mail: andymac at bullseye.apana.org.au (pref) | Snail: PO Box 370 > andymac at pcug.org.au (alt) | Belconnen ACT 2616 > Web: http://www.andymac.org/ | Australia -- John **= Email 5 ==========================** Date: Tue, 2 Dec 2003 21:59:33 +0100 From: Michael Zolk Subject: Re: UnixOS/2 distro On Sat, Nov 29, 2003 at 05:53:29PM +0100, Andreas Buening wrote: > 3. Installation tools > > A big issue are the installation and administration tools. We > already have some but they are still incomplete. Micheal, if > you're reading, could you provide some information about, which > tool does what, [...] The package on unixos2.com contains a few man pages where I tried to do just that. They probably need more work, since this is my first try. I tried to convert them to HTML using "groff -Thtml", however the result is less than convincing :| > [..] and, even more important, provide some comments > for the rexx files? Without comments the code isn't really > helpful. ;-) Even more comments? :> > These tools must have a simple interface, be absolutely bulletproof, > fast and fully reliable. Which means this task is absolutely not > simple. ;-) > > For the final implementation, I guess, we need some database which > contains all the package info, so that it is not necessary to > browse hundreds of single PKGINFO files when installing another > package. The access to this database can be written in rexx > (from scratch) or we could use other (simple) tools like perl, > python, whatever. Is there a Rexx DLL for database access? Michael -- http://www.borashop.de **= Email 6 ==========================** Date: Tue, 2 Dec 2003 22:55:41 +0000 From: John Poltorak Subject: make DIRSETGID=: install Can anyone explain what this means:- ? make DIRSETGID=: install -- John