I should have said this ages ago.
I have a working port of unicon on OpenBSD, it's in OpenBSD ports tree,
under lang/unicon
This does include a binary package for OpenBSD 2.8, at least for i386.
It's available from
ftp://ftp.openbsd.org/pub/OpenBSD/2.8/packages/i386/unicon-10.0beta.tgz
and it might be a good idea to make it available from
http://icon.cs.unlv.edu/
just to say the OpenBSD project (well, myself at least) cares.
There is one BIG problem I have with unicon: the way releases are
engineered, or rather not engineered.
I know this is still beta software, but for production purposes, having
one file which is called `uni.zip' does not cut it.
Would you consider adding a version number to it ? even uni100.zip fits
under MS-DOS.
Having one single source file that keeps changing (yes, I've seen it change
at least once) is a major pain. Not only THAT, but you should
assume that unicon is going to be a success ! and with success come users,
and with users come bug-reports.
How are you going to handle bug-reports if stuff is not reproducible ? If
you don't even know what version you're dealing with ?
So please give us a file with a version number. You probably have a shell
script somewhere that builds the uni.zip file.
Well, it's simple enough to bump the version number in such a script.
Something like this ought to do it:
# !/bin/sh
# VERSION file name
VERSION=version
if [ ! -f $VERSION ]; then
major=10
minor=0
else
. $VERSION
fi
minor=`expr $minor + 1`
echo "major=$major" >$VERSION.new
echo "minor=$minor" >>$VERSION
mv -f $VERSION.new $VERSION
ZIPFILE=uni$major$minor.zip
# Plus whatever options you need to pass to zip
zip $ZIPFILE
Sorry for not having more time to contribute to Unicon... swamped with
lots of things recently.
_______________________________________________
Unicon-group mailing list
[EMAIL PROTECTED]
http://lists.sourceforge.net/mailman/listinfo/unicon-group
