From: UnixOS2 Archive To: "UnixOS2 Archive" Date: Tue, 19 Nov 2002 04:40:56 EST-10EDT,10,-1,0,7200,3,-1,0,7200,3600 Subject: [UnixOS2_Archive] No. 373 ************************************************** Monday 18 November 2002 Number 373 ************************************************** Subjects for today 1 Re: config.site : tsikora at ntplx.net 2 PKGINFO (was: installpkg) : Michael Zolk 3 Re: MS DOC -> PDF : xyzyx" 4 Re: config.site : Andreas Buening **= Email 1 ==========================** Date: Tue, 19 Nov 2002 08:41:46 -0500 From: tsikora at ntplx.net Subject: Re: config.site Michael Zolk wrote: > > On Thu, Nov 14, 2002 at 10:53:04PM +0100, Andreas Buening wrote: > > > No, config.site is a file that is read by every configure script if > > CONFIG_SITE is set. You can put system dependend stuff there, e.g. > > transform '\' into '/' in your PATH, setting ac_executable_extensions. > > It's not a must have, but it's neither a part of the "real" system > > (/usr) nor it's some kind of "variable data" (/var). I would consider > > it as a "configuration file that can be edited by the user" (/etc) > > and is optional. It doesn't really belong to anything so I'd prefer > > to put it into the core package of the UnixOS/2 core packages. ;-) > > OK, if you can mail me your config.site, I will include it in ux2_base. > However, in the long run it might be good to create a "development core > package" that contains stuff like this. I can use it too. Can you post it here. On another note. A line should be added to installpkg/removepkg to delete the contents of the /install directory after an install. It's annoying getting the pop-up for duplicates everytime a new package is installed. -- Ted Sikora tsikora at ntplx.net **= Email 2 ==========================** Date: Tue, 19 Nov 2002 11:05:25 +0100 From: Michael Zolk Subject: PKGINFO (was: installpkg) On Sun, Nov 17, 2002 at 01:25:56AM +0100, Andreas Buening wrote: OK, just a few quick comments. > Some thoughts about your PKGINFO keywords. I encountered a lot of > questions when I read your manpages. These reflect just my ideas and > aren't well ordered: > > > PKGNAME pkgname > Where exactly is the PKGINFO file copied? > /var/lib/unixos2/packages/.??? It's copied to /var/lib/unixos2/packages/pkgname. > VERSION version-string > Make it mandatory. It would cause the maintainers to use a version > number. Installing an old version over a new one could cause an error. The problem here is that there are so many different formats the version string can have so that I don't know how to compare version numbers. Debian can do it somehow, but I don't know how. I have seen version strings like "962", "0.1", "1.2PL2", "2.4.19", "20011018" etc. > What about a "TYPE {CORE|USR|LOCAL|OPT}" keyword that specifies > which kind of package you have? USR, LOCAL or OPT packages could > be less restrictive. E.g. non CORE packages may use sh scripts > for PREINST script. Or removepkg could give an error if anybody > tries to remove a CORE package. Yes, I think we need a way to specify the priority of a package, i.e. if it's essential for UnixOS2, a pkg that most users would want to have or rather a "special interest" pkg. installpkg does not handle these priorities since it only unpacks a single pkg specified on the command line. Maybe we can have a mire user friendly installation program that handles the overall state of the distribution, i.e. fetches a list of available packages with their priorities from a local file or the web site, makes sure that all the essential pkgs are installed and checks if the dependencies for the pkgs selected for installation are met. > DESC description > Is this info printed? A message like "Do not install this package > if ..." might be helpful. If this is the case then a comment that > is not printed (REM?) might helpful, too. ? OK, I have to do some work now :). I will have to comment on your other points at a later date. Michael **= Email 3 ==========================** Date: Tue, 19 Nov 2002 18:26:16 -0600 (CST) From: "xyzyx" Subject: Re: MS DOC -> PDF On Wed, 20 Nov 2002 00:26:10 +0000, John Poltorak wrote: > >Is there such a thing as unix command line convertor of MS DOC files to >PDFs? AntiWord is the program. Website is http://www.winfield.demon.nl/ Paul **= Email 4 ==========================** Date: Tue, 19 Nov 2002 22:01:02 +0100 From: Andreas Buening Subject: Re: config.site tsikora at ntplx.net wrote: > > Michael Zolk wrote: > > > > On Thu, Nov 14, 2002 at 10:53:04PM +0100, Andreas Buening wrote: > > > > > No, config.site is a file that is read by every configure script if > > > CONFIG_SITE is set. You can put system dependend stuff there, e.g. > > > transform '\' into '/' in your PATH, setting ac_executable_extensions. > > > It's not a must have, but it's neither a part of the "real" system > > > (/usr) nor it's some kind of "variable data" (/var). I would consider > > > it as a "configuration file that can be edited by the user" (/etc) > > > and is optional. It doesn't really belong to anything so I'd prefer > > > to put it into the core package of the UnixOS/2 core packages. ;-) > > > > OK, if you can mail me your config.site, I will include it in ux2_base. > > However, in the long run it might be good to create a "development core > > package" that contains stuff like this. > > I can use it too. Can you post it here. Don't expect too much. It's not that spectacular. If anybody complains "configure screws up my PATH" or "configure can't find executables" just tell him to set CONFIG_SITE instead of starting yet another discussion about this topic. ;-) -------------------------- # This file is part of UnixOS/2. It is used by every autoconf generated # configure script if you set CONFIG_SITE=%UNIXROOT%/etc/unixos2/config.site. # You can add your own cache variables at the end of this file. echo "Loading UnixOS/2 config.site" # Executables end on ".exe". You may add other executable extensions. # Supported since autoconf 2.53 (?). test -n "$ac_executable_extensions" || ac_executable_extensions=".exe" # Replace all '\' by '/' in your PATH environment variable ux2_save_IFS="$IFS" IFS="\\" ux2_temp_PATH= for ux2_temp_dir in $PATH; do IFS="$ux2_save_IFS" if test -z "$ux2_temp_PATH"; then ux2_temp_PATH="$ux2_temp_dir" else ux2_temp_PATH="$ux2_temp_PATH/$ux2_temp_dir" fi done export PATH="$ux2_temp_PATH" unset ux2_temp_PATH unset ux2_temp_dir unset ux2_save_IFS -------------------------- [snip] Bye, Andreas -- One OS to rule them all, One OS to find them, One OS to bring them all and in the darkness bind them In the Land of Mordor where the Shadows lie.