Date: Sun, 16 May 2004 00:07:32 EST-10EDT,10,-1,0,7200,3,-1,0,7200,3600
Subject: [Ux2bs_Archive] No. 324

**************************************************
Saturday 15 May 2004
 Number  324
**************************************************

Subjects for today
 
1   Another test post - please ignore : Jon Saxton" <spam.trap at verizon.net>
2  Re:  Another test post - please ignore : IanM" <IanM>
3  Re:  Another test post - please ignore : Jon Saxton" <spam.trap at verizon.net>
4  Re:  Another test post - please ignore : John Poltorak <jp at warpix.org>
5  Re:  New pages : Anton Monroe <akm at meer.net>
6  Re:  New pages : T.Sikora" <tsikora at ntplx.net>
7   Dialog install : T.Sikora" <tsikora at ntplx.net>
8  Re:  New pages : John Poltorak <jp at warpix.org>
9  Re:  New pages : T.Sikora" <tsikora at ntplx.net>
10  Re:  New pages : John Poltorak <jp at warpix.org>
11  Re: [Fwd:  Dialog install] : T.Sikora" <tsikora at ntplx.net>
12  Re:  New pages : T.Sikora" <tsikora at ntplx.net>
13  Re: [Fwd:  Dialog install] : T.Sikora" <tsikora at ntplx.net>
14  Re: [Fwd:  Dialog install] : T.Sikora" <tsikora at ntplx.net>
15   cohesion or super glue on your fingers? : T.Sikora" <tsikora at ntplx.net>
16  Re: [Fwd:  Dialog install] : Andreas Buening <andreas.buening at nexgo.de>


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

Date:  Fri, 14 May 2004 10:14:13 -0400
From:  "Jon Saxton" <spam.trap at verizon.net>
Subject:   Another test post - please ignore

Haven't seen a message since Wedndesday and just checking to ensure that Earth
wasn't demolished by Vogons to make way for a hyperspace bypass ...

--
Jon Saxton <js at triton.vg> Developer of cross-platform software for UNIX, Windows and OS/2
U.S. agent for Triton Technologies International Ltd
http://www.triton.vg/
_______________________________________________
UX2BS mailing list
UX2BS at os2ports.com
http://os2ports.com/mailman/listinfo/ux2bs

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

Date:  Sat, 15 May 2004 00:20:06 +1000 (EST)
From:  "IanM" <IanM>
Subject:  Re:  Another test post - please ignore

> Haven't seen a message since Wedndesday and just checking to ensure that Earth
> wasn't demolished by Vogons to make way for a hyperspace bypass ...

I believe that happens on Friday

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

Never spit in a man's face unless his moustache is on fire.  --Henry Root
_______________________________________________
UX2BS mailing list
UX2BS at os2ports.com
http://os2ports.com/mailman/listinfo/ux2bs

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

Date:  Fri, 14 May 2004 10:25:36 -0400
From:  "Jon Saxton" <spam.trap at verizon.net>
Subject:  Re:  Another test post - please ignore

** Reply to note from "IanM" <IanM> on Sat, 15 May 2004
00:20:06 +1000 (EST)

> > Haven't seen a message since Wedndesday and just checking to ensure that Earth
> > wasn't demolished by Vogons to make way for a hyperspace bypass ...
> 
> I believe that happens on Friday

Ah, yes, you're right.  And quite soon, too.  Anyone for a pint at the pub?

--
Jon Saxton <js at triton.vg> Developer of cross-platform software for UNIX, Windows and OS/2
U.S. agent for Triton Technologies International Ltd
http://www.triton.vg/
_______________________________________________
UX2BS mailing list
UX2BS at os2ports.com
http://os2ports.com/mailman/listinfo/ux2bs

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

Date:  Fri, 14 May 2004 15:28:23 +0100
From:  John Poltorak <jp at warpix.org>
Subject:  Re:  Another test post - please ignore

On Fri, May 14, 2004 at 10:25:36AM -0400, Jon Saxton wrote:
> ** Reply to note from "IanM" <IanM> on Sat, 15 May 2004
> 00:20:06 +1000 (EST)
> 
> > > Haven't seen a message since Wedndesday and just checking to ensure that Earth
> > > wasn't demolished by Vogons to make way for a hyperspace bypass ...
> > 
> > I believe that happens on Friday
> 
> Ah, yes, you're right.  And quite soon, too.  Anyone for a pint at the pub?

That's the best suggestion I've ever seen on this list!

> --
> Jon Saxton <js at triton.vg> Developer of cross-platform software for UNIX, Windows and OS/2
> U.S. agent for Triton Technologies International Ltd


-- 
John


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

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

Date:  Fri, 14 May 2004 22:49:53 -0500
From:  Anton Monroe <akm at meer.net>
Subject:  Re:  New pages

On Wed, May 12, 2004 at 01:53:33PM -0400, T.Sikora wrote:
> The spinoff project UX2 Redux is meant as an interim release or 
> framework for the UX2 distribution until it becomes available. It may or 
> may not resemble the yet to be released distribution but provides an 
> immediate working platform for OS2-Unix ports as a stop gap measure that 
> is based on both the UX2BS and UX2. All current developments will be 
> implemented when made available. 'Purist' conventions take a backseat 
> for the sake of  'urgency' and binaries may or may not have been built 
> with the system. The ultimate goal is for them to be built and packaged 
> entirely with UX2.

I'm delighted to hear that.  I'm no purist myself, I just want to be
able to build things I want.  John does seem to be a purist (perhaps an
obsessive-compulsive personality? <g>), but that's exactly the kind of 
person that a project like this needs.  I trust that the directory
trees, etc. will be coordinated so John's improvements can be easily
integrated.

To save confusion on the mailing list, how should I refer to the two
branches?  "stable" and "development"?  "practical" and "purist"?

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

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

Date:  Sat, 15 May 2004 07:28:07 -0400
From:  "T.Sikora" <tsikora at ntplx.net>
Subject:  Re:  New pages

Anton Monroe wrote:
> On Wed, May 12, 2004 at 01:53:33PM -0400, T.Sikora wrote:
> 
>>The spinoff project UX2 Redux is meant as an interim release or 
>>framework for the UX2 distribution until it becomes available. It may or 
>>may not resemble the yet to be released distribution but provides an 
>>immediate working platform for OS2-Unix ports as a stop gap measure that 
>>is based on both the UX2BS and UX2. All current developments will be 
>>implemented when made available. 'Purist' conventions take a backseat 
>>for the sake of  'urgency' and binaries may or may not have been built 
>>with the system. The ultimate goal is for them to be built and packaged 
>>entirely with UX2.
> 
> 
> I'm delighted to hear that.  I'm no purist myself, I just want to be
> able to build things I want.  John does seem to be a purist (perhaps an
> obsessive-compulsive personality? <g>), 

<laughs> he's the glue that keeps us together.

but that's exactly the kind of
> person that a project like this needs.  I trust that the directory
> trees, etc. will be coordinated so John's improvements can be easily
> integrated.
> 
> To save confusion on the mailing list, how should I refer to the two
> branches?  "stable" and "development"?  "practical" and "purist"?
> 

Nah, the UX2BS is the UX2BS. Redux is just a temporary version of the 
UX2 distribution. It combines the best features of the Build System with 
the UX2 distribution. Mostly it was created to build a proper install 
and packaging system for the distribution. I agree with John's 'purist' 
conventions but it is much easier to make it so with a working system 
and replace the parts than starting from the ground up. I believe we can 
have a better overview of how it should be this way.

Some of the guys on the list have been wanting to build a dialog driven 
install. This gives them the perfect oppurtunity. I pretty much want an 
integrated development environment and packaging tools aka a 'real' 
distribution. What I see is:

UX2BS = Core UX2 developers ie; UX2BS list, etc
UX2(aka Redux)  = Distribution maintainers ie; UX2 list, Stupid name I 
know.

UX2ports = Ports tree and port maintainers list, etc  This can be part 
of UX2BS for now but it should be seperate eventually.

We need to do this or we will never get out of the basement/garage?

This thing has been at the crossroads for some time. We been over this 
stuff for several years. What we really need is a good kick in the a** 
to move forward. We been doing the same stuff over, and over, and over, 
and over, and over............

A lot of the folks using this stuff are not developers and want to 
participate and *need* a working unix environment. This should give it 
to them right now.

-- 
T.Sikora
tsikora at ntplx dot net




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

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

Date:  Sat, 15 May 2004 07:50:30 -0400
From:  "T.Sikora" <tsikora at ntplx.net>
Subject:   Dialog install

The bootstrap is a brilliant invention but mostly for developers only. 
What is needed is a standard install method that can download the 
required packages(zips) and set up the basic environment and optionally 
pick the packages you wish to install. Sort of like NetBSD or OpenBSD.

What I'm waiting for is Johns's OK and/or blessing? to make the UX2 list 
for this stuff and the distribution and related stuff. And please don't 
say we have too many lists or OS2-Unix is the UX2 list. IT's NOT. It's a 
general help forum for Unix ports and seems to be a coverall . Many and 
most of the members have no involvemnt at all. If anyone one really 
wants this we need to do these things. UnixOS2.org needs to be rewritten 
  as a Unix Distribution site and not a pile of disjointed ports.

This is my take on it anyways. Were so close but so far. Mostly 
disorganized. All the tools are at our disposal.


Any objections to:

UX2BS  - UX2 Core Developers
UX2    - UX2 Distribution

Mailing Lists?

-- 
T.Sikora
tsikora at ntplx dot net




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

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

Date:  Sat, 15 May 2004 12:43:33 +0100
From:  John Poltorak <jp at warpix.org>
Subject:  Re:  New pages

On Sat, May 15, 2004 at 07:28:07AM -0400, T.Sikora wrote:
> Anton Monroe wrote:

> Nah, the UX2BS is the UX2BS. Redux is just a temporary version of the 
> UX2 distribution. It combines the best features of the Build System with 
> the UX2 distribution. 

In a way Redux provides some sort of vision of where we won't to get to 
and is useful as a plug 'n play system for those that want it. I see it as 
my task to get to where Redux is via an empirical route where the 
development environment is fully reproducible from just a few key 
components. This will help maintenance in the long run because there will 
not be a reliance on specific porters to provide us with out OS/2 ports.

> Mostly it was created to build a proper install 
> and packaging system for the distribution. I agree with John's 'purist' 
> conventions but it is much easier to make it so with a working system 
> and replace the parts than starting from the ground up. I believe we can 
> have a better overview of how it should be this way.
> 
> Some of the guys on the list have been wanting to build a dialog driven 
> install. 

A dialog based install is already available from Slackware and it 
shouldn't be too difficult to get that working on OS/2.

> A lot of the folks using this stuff are not developers and want to 
> participate and *need* a working unix environment. This should give it 
> to them right now.


We still have the problem that we don't have a standard automated PKG 
making facility.


 
> -- 
> T.Sikora
> tsikora at ntplx dot net


-- 
John


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

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

Date:  Sat, 15 May 2004 08:19:14 -0400
From:  "T.Sikora" <tsikora at ntplx.net>
Subject:  Re:  New pages

John Poltorak wrote:
> On Sat, May 15, 2004 at 07:28:07AM -0400, T.Sikora wrote:
> 
>>Anton Monroe wrote:
> 
> 
>>Nah, the UX2BS is the UX2BS. Redux is just a temporary version of the 
>>UX2 distribution. It combines the best features of the Build System with 
>>the UX2 distribution. 
> 
> 
> In a way Redux provides some sort of vision of where we won't to get to 
> and is useful as a plug 'n play system for those that want it. I see it as 
> my task to get to where Redux is via an empirical route where the
> development environment is fully reproducible from just a few key 
> components. 

That is exactly how I see it.

This will help maintenance in the long run because there will
> not be a reliance on specific porters to provide us with out OS/2 ports.
> 
> 
>>Mostly it was created to build a proper install 
>>and packaging system for the distribution. I agree with John's 'purist' 
>>conventions but it is much easier to make it so with a working system 
>>and replace the parts than starting from the ground up. I believe we can 
>>have a better overview of how it should be this way.
>>
>>Some of the guys on the list have been wanting to build a dialog driven 
>>install. 
> 
> 
> A dialog based install is already available from Slackware and it 
> shouldn't be too difficult to get that working on OS/2.
> 

That was what I was thinking but with Net/OpenBSD's ftp option to grab
it from unixos2.com and mirrors too. CD or FTP install option.

> 
>>A lot of the folks using this stuff are not developers and want to 
>>participate and *need* a working unix environment. This should give it 
>>to them right now.
> 
> 
> 
> We still have the problem that we don't have a standard automated PKG 
> making facility.
> 
You may have missed these. These were submitted in August last year.
I never tested them but they are said to work.

Makepkg, they are still in os2ports incoming.

ftp://os2ports.com/incoming

If anything this frees your hands somewhat so that some can work 
simultaneously on the distribution. Some do the install, some refine the 
package tools, etc. Of course all are answerable to what UX2BS aka core 
developers dictate *BUT* we make concessions to allow outside ports to 
keep it complete until they are buildable and replaced.

-- 
T.Sikora
tsikora at ntplx dot net




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

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

Date:  Sat, 15 May 2004 13:16:40 +0100
From:  John Poltorak <jp at warpix.org>
Subject:  Re:  New pages

On Sat, May 15, 2004 at 08:19:14AM -0400, T.Sikora wrote:

> > We still have the problem that we don't have a standard automated PKG 
> > making facility.
> > 
> You may have missed these. These were submitted in August last year.
> I never tested them but they are said to work.
> 
> Makepkg, they are still in os2ports incoming.
> 
> ftp://os2ports.com/incoming

I don't know how that works, but what we need is something that integrates 
into the build system and creates a PKG target in the makefile and knows 
automatically which files need to be included in a distributed archive.

There may well be something already created by Automake which helps in 
this, but I haven't spotted it so far.

> -- 
> T.Sikora
> tsikora at ntplx dot net


-- 
John



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

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

Date:  Sat, 15 May 2004 08:32:22 -0400
From:  "T.Sikora" <tsikora at ntplx.net>
Subject:  Re: [Fwd:  Dialog install]

Jeff Robinson wrote:
> T.Sikora wrote:
> 
>>
>> The bootstrap is a brilliant invention but mostly for developers only. 
>> What is needed is a standard install method that can download the 
>> required packages(zips) and set up the basic environment and 
>> optionally pick the packages you wish to install. Sort of like NetBSD 
>> or OpenBSD.
>>
> 
> Yup!
> 
> What we need is an environment that is smart enough not only to download 
> the stuff and put it in the right location, but also to do any 
> file-configuration stuff.  Theoretically we should never touch the 
> config.sys outside of perhaps an initial installation package, though I 
> think you've proven that even that could be avoided with your first 
> version of the UX2Redux.
> 
>> What I'm waiting for is Johns's OK and/or blessing? to make the UX2 
>> list for this stuff and the distribution and related stuff. And please 
>> don't say we have too many lists or OS2-Unix is the UX2 list. IT's 
>> NOT. It's a general help forum for Unix ports and seems to be a 
>> coverall . Many and most of the members have no involvemnt at all. If 
>> anyone one really wants this we need to do these things. UnixOS2.org 
>> needs to be rewritten  as a Unix Distribution site and not a pile of 
>> disjointed ports.
>>
> 
> Right now the lists seem to be a bit of a mish-mash of UX2BS stuff in 

UX2BS occassionally has been turning into a clone of OS2-Unix, not a bad 
thing, but we are easily taken way off track.

> UnixOS2 lists, so I think the distinction right now has gotten a bit 
> blurred.  It'd be good to have that cleared up... and basically I'm cool 
> with whatever you choose to do as far as the lists go.
> 
> You're right about the site, though.  We need to redo UnixOS2.org 
> because as you said, it's sort've a Unix-centric version of Hobbes.  I 
> would like to go through and rename the packages properly as well... 
> y'know, sort've like I suggested on: 
> http://unixos2.com/pages/UX2-PackageCreationHOW-TO.html
> (in the "Naming Conventions" section).

I guess I should look there more often.. did not know it existed.
This is another reason for cohesion like you said.

> 
> I think I may've mentioned that I had also created a tool that will take 
> UX2 archives in the pkg format and almost automagically convert them to 
> WarpIN archives as well.  This might be something interesting for future 
> consideration.  One nice thing about WarpIn is that it has built in 
> capabilities for manipulating text files during install/uninstall.  But 
> I digress!
> 
> The thing I'm thinking is that it would be nice for archives to automate 
> as much of the packaging as possible.  Perhaps I should look into 
> designing a text-based package-building tool, too?

Geez it exists.
ftp://os2ports.com/incoming  makepkg

> 
>> This is my take on it anyways. Were so close but so far. Mostly 
>> disorganized. All the tools are at our disposal.
>>
> 
> What we need is someone to lay out a road-map and/or delegate.  I think 
> that is one problem right now... everything is done by a single person. 
>  I do think that initially you need a focused core of just a few people 
> that can accept new stuff, just so you can keep some coherency to the 
> project.

I see UX2BS building the key components and routines we require.

> 
>>
>> Any objections to:
>>
>> UX2BS  - UX2 Core Developers
>> UX2    - UX2 Distribution
>>
>> Mailing Lists?
>>
> 
> Do you want me to jot down some ideas of things that I'd like to see, or 
> concept of different directions I'd like to explore?

Yeah, we need more vision.

> 
> Jeff
> 


-- 
T.Sikora
tsikora at ntplx dot net




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

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

Date:  Sat, 15 May 2004 08:37:18 -0400
From:  "T.Sikora" <tsikora at ntplx.net>
Subject:  Re:  New pages

This is a multi-part message in MIME format.
--------------090803030302090906090305
Content-Type: text/plain; charset=us-ascii; format=flowed
Content-Transfer-Encoding: 7bit

John Poltorak wrote:
> On Sat, May 15, 2004 at 08:19:14AM -0400, T.Sikora wrote:
> 
> 
>>>We still have the problem that we don't have a standard automated PKG 
>>>making facility.
>>>
>>
>>You may have missed these. These were submitted in August last year.
>>I never tested them but they are said to work.
>>
>>Makepkg, they are still in os2ports incoming.
>>
>>ftp://os2ports.com/incoming
> 
> 
> I don't know how that works, but what we need is something that integrates 
> into the build system and creates a PKG target in the makefile and knows 
> automatically which files need to be included in a distributed archive.

Orignally I was asking for a command to add to 'build'
or build <port> -pkg  This was submitted after much discussion but I 
never did try it.

> 
> There may well be something already created by Automake which helps in 
> this, but I haven't spotted it so far.
> 
The slackware routine is very simple see attchment We really should try 
those submissions first.

> 
>>-- 
>>T.Sikora
>>tsikora at ntplx dot net
> 
> 
> 


-- 
T.Sikora
tsikora at ntplx dot net





--------------090803030302090906090305
Content-Type: text/plain;
 name="makepkg"
Content-Transfer-Encoding: 7bit
Content-Disposition: inline;
 filename="makepkg"

#!/bin/sh
# Copyright 1994, 1998  Patrick Volkerding, Moorhead, Minnesota USA 
# Copyright 2003  Slackware Linux, Inc.  Concord, CA USA
# All rights reserved.
#
# Redistribution and use of this script, with or without modification, is
# permitted provided that the following conditions are met:
#
# 1. Redistributions of this script must retain the above copyright
#    notice, this list of conditions and the following disclaimer.
#
#  THIS SOFTWARE IS PROVIDED BY THE AUTHOR ``AS IS'' AND ANY EXPRESS OR IMPLIED
#  WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF
#  MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE DISCLAIMED.  IN NO
#  EVENT SHALL THE AUTHOR BE LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL,
#  SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING, BUT NOT LIMITED TO,
#  PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES; LOSS OF USE, DATA, OR PROFITS;
#  OR BUSINESS INTERRUPTION) HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY,
#  WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR
#  OTHERWISE) ARISING IN ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF
#  ADVISED OF THE POSSIBILITY OF SUCH DAMAGE.
#
# Wed Mar 18 15:32:33 CST 1998
# Patched to avoid possible symlink attacks in /tmp.

TAR=tar-1.13
$TAR --help 1> /dev/null 2> /dev/null
if [ ! $? = 0 ]; then
  TAR=tar
fi
if [ ! "`LC_MESSAGES=C $TAR --version`" = "tar (GNU tar) 1.13

Copyright (C) 1988, 92,93,94,95,96,97,98, 1999 Free Software Foundation, Inc.
This is free software; see the source for copying conditions.  There is NO
warranty; not even for MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE.

Written by John Gilmore and Jay Fenlason." ]; then
  echo "WARNING: pkgtools are unstable with tar > 1.13."
  echo "         You should provide a \"tar-1.13\" in your \$PATH."
  sleep 5
fi

make_install_script() {
  COUNT=1
  LINE="`sed -n "$COUNT p" $1`"
  while [ ! "$LINE" = "" ]; do
   LINKGOESIN="`echo "$LINE" | cut -f 1 -d " "`" 
   LINKGOESIN="`dirname $LINKGOESIN`" 
   LINKNAMEIS="`echo "$LINE" | cut -f 1 -d ' '`"
   LINKNAMEIS="`basename "$LINKNAMEIS"`"
   LINKPOINTSTO="`echo "$LINE" | cut -f 3 -d ' '`"
   echo "( cd $LINKGOESIN ; rm -rf $LINKNAMEIS )"
   echo "( cd $LINKGOESIN ; ln -sf $LINKPOINTSTO $LINKNAMEIS )"
   COUNT=`expr $COUNT + 1`
   LINE="`sed -n "$COUNT p" $1`"
  done
}

usage() {
  cat << EOF

Usage: makepkg package_name.tgz

Makes a Slackware compatible "*.tgz" package containing the contents of the 
current and all subdirectories. If symbolic links exist, they will be removed
and an installation script will be made to recreate them later. This script
will be called "install/doinst.sh". You may add any of your own ash-compatible
shell scripts to this file and rebuild the package if you wish.

options:      -l, --linkadd y|n (moves symlinks into doinst.sh: recommended)
              -c, --chown y|n (resets all permissions to root:root 755
                               - not generally recommended)

If these options are not set, makepkg will prompt as appropriate.
EOF
}

TMP=/tmp # This can be a hole, but I'm going to be careful about file
         # creation in there, so don't panic. :^)

# Parse options
while [ 0 ]; do
  if [ "$1" = "--linkadd" -o "$1" = "-l" ]; then
    if [ "$2" = "y" ]; then
      LINKADD=y
    elif [ "$2" = "n" ]; then
      LINKADD=n
    else
      usage
      exit 2
    fi
    shift 2
  elif [ "$1" = "--chown" -o "$1" = "-c" ]; then
    if [ "$2" = "y" ]; then
      CHOWN=y
    elif [ "$2" = "n" ]; then
      CHOWN=n
    else
      usage
      exit 2
    fi
    shift 2
  elif [ "$1" = "-h" -o "$1" = "-H" -o "$1" = "--help" -o $# = 0 ]; then
    usage
    exit 0
  else
    break
  fi
done

echo
echo "Slackware package maker, version 2.1."
PACKAGE_NAME=$1
TARGET_NAME="`dirname $PACKAGE_NAME`"
PACKAGE_NAME="`basename $PACKAGE_NAME`"
TAR_NAME="`basename $PACKAGE_NAME .tgz`"
echo
echo "Searching for symbolic links:"
# Get rid of possible pre-existing trouble:
INST=`mktemp $TMP/makepkg.XXXXXX`
# This requires the ls from coreutils-5.0 (or newer):
find . -type l -exec ls -l --time-style=long-iso {} \; | while read foo ; do echo $foo ; done | cut -f 8- -d ' ' | cut -b3- | tee $INST
if [ ! "`cat $INST`" = "" ]; then
  echo
  echo "Making symbolic link creation script:"
  make_install_script $INST | tee doinst.sh
fi
echo
if [ ! "`cat $INST`" = "" ]; then
  if [ -r install/doinst.sh ]; then
    echo "Unless your existing installation script already comtains the code"
    echo "to create these links, you should append these lines to your existing"
    echo "install script. Now's your chance. :^)"
    echo
    echo "Would you like to add this stuff to the existing install script and"
    echo -n "remove the symbolic links ([y]es, [n]o)? "
  else
    echo "It is recommended that you make these lines your new installation script."
    echo
    echo "Would you like to make this stuff the install script for this package"
    echo -n "and remove the symbolic links ([y]es, [n]o)? "
  fi
  if [ ! "$LINKADD" ]; then
    read LINKADD;
    echo
  else
    echo $LINKADD
    echo
  fi
  if [ "$LINKADD" = "y" ]; then
    if [ -r install/doinst.sh ]; then
      UPDATE="t"
      cat doinst.sh >> install/doinst.sh
    else
      mkdir install
      cat doinst.sh > install/doinst.sh
    fi
    echo
    echo "Removing symbolic links:"
    find . -type l -exec rm -v {} \;
    echo
    if [ "$UPDATE" = "t" ]; then
      echo "Updating your ./install/doinst.sh..."
    else
      echo "Creating your new ./install/doinst.sh..."
    fi
  fi
else
  echo "No symbolic links were found, so we won't make an installation script."
  echo "You can make your own later in ./install/doinst.sh and rebuild the"
  echo "package if you like."
fi
rm -f doinst.sh $INST
echo
echo "This next step is optional - you can set the directories in your package"
echo "to some sane permissions. If any of the directories in your package have"
echo "special permissions, then DO NOT reset them here!"
echo 
echo "Would you like to reset all directory permissions to 755 (drwxr-xr-x) and"
echo -n "directory ownerships to root.root ([y]es, [n]o)? "
if [ ! "$CHOWN" ]; then
  read CHOWN;
  echo
else
  echo $CHOWN
  echo
fi
if [ "$CHOWN" = "y" ]; then
  find . -type d -exec chmod -v 755 {} \; 
  find . -type d -exec chown -v root.root {} \;
fi
echo
echo "Creating tar file $TAR_NAME.tar..."
echo
$TAR cvf $TAR_NAME.tar .
# Warn of zero-length files:
find . -type f -size 0c | while read file ; do
  echo "WARNING: zero length file $file"
done
find . -type f -name '*.gz' -size 20c | while read file ; do
  echo "WARNING: possible empty gzipped file $file"
done
echo
echo "Gzipping $TAR_NAME.tar..."
gzip -9 $TAR_NAME.tar
echo
echo "Renaming $TAR_NAME.tar.gz to $PACKAGE_NAME..."
mv $TAR_NAME.tar.gz $PACKAGE_NAME
if [ ! "$TARGET_NAME" = "." ]; then
  echo
  echo "Moving $PACKAGE_NAME to $TARGET_NAME..."
  mv $PACKAGE_NAME $TARGET_NAME
fi
echo
echo "Package creation complete."
echo

--------------090803030302090906090305
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
Content-Disposition: inline

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

--------------090803030302090906090305--

**= Email   13 ==========================**

Date:  Sat, 15 May 2004 08:59:56 -0400
From:  "T.Sikora" <tsikora at ntplx.net>
Subject:  Re: [Fwd:  Dialog install]

T.Sikora wrote:
> Jeff Robinson wrote:
> 
>> T.Sikora wrote:
>>
>>>

>>
>> What we need is someone to lay out a road-map and/or delegate.  I 
>> think that is one problem right now... everything is done by a single 
>> person.  I do think that initially you need a focused core of just a 
>> few people that can accept new stuff, just so you can keep some 
>> coherency to the project.
> 
> 
> I see UX2BS building the key components and routines we require.
> 
>>

That is their resonibility and to map the development environment and 
make the development tool packages available to us for the distribution.
If the developer 'option' on the UX2 install is chosen you should be 
able to build and package those same things and anything else. The rest 
of the ports is an entirely different matter. They are maintained in the 
'ports tree' and packaged as the 'opt' picks for the install. Of course 
you can simply build it yourself after the intial install with the 
'development' tools option and run 'build <port>' in the directory for 
the desired port. This all works in redux now. Maybe we should just drop 
Redux formally but use it as this release candidates alias like 
Mandrake/Redhat do. Publicly it should just be UX2 Distribution?

Yes X is finally in /usr so first thing would be to see if it all still 
works and replace 4.3.0 with 4.4.0.

UX2BS has to make concessions and allow us to use 'third party ports' 
for the sake of cohesion and maintaining a full distribution. After the 
basic install and mechanisims are in place completeing the build 
environment and making it reproducable with UX2 is probably the 
priority. We don't have to be current(port wise)only key components like 
zlib, etc., if it builds and works use it for now. That should be the 
last step when it's completed.


Phew! I guess it's time for everyone else's take on this.
-- 
T.Sikora
tsikora at ntplx dot net




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

**= Email   14 ==========================**

Date:  Sat, 15 May 2004 09:09:45 -0400
From:  "T.Sikora" <tsikora at ntplx.net>
Subject:  Re: [Fwd:  Dialog install]

Jeff Robinson wrote:
> T.Sikora wrote:
> 
>> Jeff Robinson wrote:
>>
>>> T.Sikora wrote:
>>>
>>>>
>>>> The bootstrap is a brilliant invention but mostly for developers 
>>>> only. What is needed is a standard install method that can download 
>>>> the required packages(zips) and set up the basic environment and 
>>>> optionally pick the packages you wish to install. Sort of like 
>>>> NetBSD or OpenBSD.
>>>>
>>>
>>> Yup!
>>>
>>> What we need is an environment that is smart enough not only to 
>>> download the stuff and put it in the right location, but also to do 
>>> any file-configuration stuff.  Theoretically we should never touch 
>>> the config.sys outside of perhaps an initial installation package, 
>>> though I think you've proven that even that could be avoided with 
>>> your first version of the UX2Redux.
>>>
>>>> What I'm waiting for is Johns's OK and/or blessing? to make the UX2 
>>>> list for this stuff and the distribution and related stuff. And 
>>>> please don't say we have too many lists or OS2-Unix is the UX2 list. 
>>>> IT's NOT. It's a general help forum for Unix ports and seems to be a 
>>>> coverall . Many and most of the members have no involvemnt at all. 
>>>> If anyone one really wants this we need to do these things. 
>>>> UnixOS2.org needs to be rewritten  as a Unix Distribution site and 
>>>> not a pile of disjointed ports.
>>>>
>>>
>>> Right now the lists seem to be a bit of a mish-mash of UX2BS stuff in 
>>
>>
>>
>> UX2BS occassionally has been turning into a clone of OS2-Unix, not a 
>> bad thing, but we are easily taken way off track.
>>
> 
> I think that's one the of the arguments for having the direction 
> actually written out where everybody can see where we're trying to go 
> with each project.  For the longest time I didn't know specifically 
> where UX2BS was headed either, which caused me confusion... one 
> particular instance was the UX2ROOT variable that suddenly disappeared. 
>  Though I think I'm *much* better now!
> 
>>> UnixOS2 lists, so I think the distinction right now has gotten a bit 
>>> blurred.  It'd be good to have that cleared up... and basically I'm 
>>> cool with whatever you choose to do as far as the lists go.
>>>
>>> You're right about the site, though.  We need to redo UnixOS2.org 
>>> because as you said, it's sort've a Unix-centric version of Hobbes.  
>>> I would like to go through and rename the packages properly as 
>>> well... y'know, sort've like I suggested on: 
>>> http://unixos2.com/pages/UX2-PackageCreationHOW-TO.html
>>> (in the "Naming Conventions" section).
>>
>>
>>
>> I guess I should look there more often.. did not know it existed.
>> This is another reason for cohesion like you said.
>>
> 
> I'll gladly take care of pages for both UnixOS2 and UX2Redux if you want 
> to feed me information on it.  (Or you can come up with a better content 
> management system that I can use)!

ZOPE? Did you say Zope. That greatly simplifies things and allows 
multiple page maintainers. All this stuff is too much for one or even a 
few people. We need volunteers to maintain certain aspects of 
everything. pkgtools, install, filesystem, etc. The guy who does the ex; 
pkgtools does the pkgtools section in Zope, etc. Only takes a second 
through your browser.

> 
>>>
>>> I think I may've mentioned that I had also created a tool that will 
>>> take UX2 archives in the pkg format and almost automagically convert 
>>> them to WarpIN archives as well.  

Theres that 'dirty'<laughs> word again. Too much animosity towards it 
for now.

This might be something interesting
>>> for future consideration.  One nice thing about WarpIn is that it has 
>>> built in capabilities for manipulating text files during 
>>> install/uninstall.  But I digress!
>>>
>>> The thing I'm thinking is that it would be nice for archives to 
>>> automate as much of the packaging as possible.  Perhaps I should look 
>>> into designing a text-based package-building tool, too?
>>
>>
>>
>> Geez it exists.
>> ftp://os2ports.com/incoming  makepkg
>>
> 
> Whoops!  There goes that cohesion thing again!  Has your left hand been 
> beatin' on my right hand again?  

Watch it you may go blind.. couldn't resist!! Slap me now.

Either way, I think this'll be a
> healthy turn for the projects so that nobody gets bruised up too badly, 
> both can coexist and actually benefit from each other.
> 
>>>
>>>> This is my take on it anyways. Were so close but so far. Mostly 
>>>> disorganized. All the tools are at our disposal.
>>>>
>>>
>>> What we need is someone to lay out a road-map and/or delegate.  I 
>>> think that is one problem right now... everything is done by a single 
>>> person.  I do think that initially you need a focused core of just a 
>>> few people that can accept new stuff, just so you can keep some 
>>> coherency to the project.
>>
>>
>>
>> I see UX2BS building the key components and routines we require.
>>
> 
> Sounds good.... and then just supplementing with other packages until we 
> can get UX2BS to build all of the ones we want?
> 
>>>
>>>>
>>>> Any objections to:
>>>>
>>>> UX2BS  - UX2 Core Developers
>>>> UX2    - UX2 Distribution
>>>>
>>>> Mailing Lists?
>>>>
>>>
>>> Do you want me to jot down some ideas of things that I'd like to see, 
>>> or concept of different directions I'd like to explore?
>>
>>
>>
>> Yeah, we need more vision.
>>
> 
> We may not have vision yet, but at least we're getting a prescription 
> together!
> 
> Though I'd like night vision.  Or laser vision.  That'd be pretty cool.
> 
> Jeff
> 

Coffee time!

-- 
T.Sikora
tsikora at ntplx dot net




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

**= Email   15 ==========================**

Date:  Sat, 15 May 2004 09:17:54 -0400
From:  "T.Sikora" <tsikora at ntplx.net>
Subject:   cohesion or super glue on your fingers?

We were straying way, way off course. If anything at least a shared 
vison or plan will come from this. Me like a lot of other people don't 
have a clue as to what's going on.

-- 
T.Sikora
tsikora at ntplx dot net





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

**= Email   16 ==========================**

Date:  Sat, 15 May 2004 15:54:31 +0200
From:  Andreas Buening <andreas.buening at nexgo.de>
Subject:  Re: [Fwd:  Dialog install]

T.Sikora wrote:
> 
> Jeff Robinson wrote:

> > The thing I'm thinking is that it would be nice for archives to automate
> > as much of the packaging as possible.  Perhaps I should look into
> > designing a text-based package-building tool, too?
> 
> Geez it exists.
> ftp://os2ports.com/incoming  makepkg

I haven't followed the discussion closely. However, a working
package installation system is highly needed. Therefore, some
time ago, Michael Zolk and me started to rewrite his installpkg
tools and that makepkg tool mentioned above. I didn't want
to make an announcement before we had anything working because
I don't like vaporware. Due to the usual lack of time problem
things didn't go on as they should. :-(

However, some general organizational stuff would be also
very helpful. This includes someone who keeps the website
up to date, especially the info sites for the packages,
the bug lists, the FAQ, someone who bothers the developers
until they tell him what's news about package xyz.
Someone who maintains the final distribution, someone who
decides which version of which package will go into it,
what's the naming convention on the "installation CD" ;-).
Personally, I don't care whether grep is in the "a1" or
"d2" or "baseutils" or whatever tree. And this is something
a developer doesn't need to know, it's more likely that this
kind of micromanagement leads to wasting time that could
be spent more effectively on porting software packages.


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