Index of /afterstep//download/ascp
Name Last modified Size Description
Parent Directory 12-Apr-2007 15:53 -
README 20-Sep-2005 10:28 2k
ascp-0.9.3.tar.gz 20-Sep-2005 10:28 144k
ascp-0.9.3.tar.gz.asc 20-Sep-2005 10:28 1k
ascp-0.9.4.tar.gz 20-Sep-2005 10:28 165k
ascp-0.9.4.tar.gz.asc 20-Sep-2005 10:28 1k
ascp-0.9.5.tar.gz 20-Sep-2005 10:28 175k
ascp-0.9.5.tar.gz.asc 20-Sep-2005 10:28 1k
ascp-0.9.6pre.tar.gz 20-Sep-2005 10:28 177k
ascp-0.9.6pre.tar.gz..> 20-Sep-2005 10:28 1k
ascp-1.0.1.tar.gz 20-Sep-2005 10:28 190k
ascp-1.0.1.tar.gz.asc 20-Sep-2005 10:28 1k
ascp-1.0.2.tar.gz 20-Sep-2005 10:28 190k
ascp-1.0.2.tar.gz.asc 20-Sep-2005 10:28 1k
ascp-1.0.3.tar.gz 20-Sep-2005 10:28 188k
ascp-1.0.3.tar.gz.asc 20-Sep-2005 10:28 1k
ascp-1.0.tar.gz 20-Sep-2005 10:27 185k
ascp-1.0.tar.gz.asc 20-Sep-2005 10:28 1k
General Information
===================
This is ascp version 1.0.3!
(Un)fortunately, this is the final release of this version. The next
incarnation (1.2) shall be such a butt-kicker, so please stay tuned to
#afterstep, and #ascp.
(I mean it this time. I have also released a preview of ascp-1.2 which is
"not" to be used to configure _anything_ yet).
It was compiled succesfully using the gtk+-1.2.1 and glib+1.2.1
You can pick them up at: ftp://ftp.gimp.org/pub/gtk
-- deprecated, use the gtk-step theme instead
For even better looks, you can also pick up the latest version
of GTkstep from:
http://www-info2.informatik.uni-wuerzburg.de/staff/ulli/gtkstep/
---
The official web site is:
http://hubble.colorado.edu/~nwanua/htmldir/ascp.html
It's still a good idea to make a copy of your config files :-)
Plans are being made to preserve and make backups of config files
before they are edited.
Installation
============
See the file 'INSTALL'
Internationalization
====================
See the file README.I18N
Known bugs
==================
See the file 'BUGS'
How to report bugs
==================
To report a bug, please send mail to nwanua@colorado.edu
In the mail include:
* The version of ascp
* The version of GTK
* Information about your system. For instance:
- What operating system and version
- What version of X
- For Linux, what version of the C library
And anything else you think is relevant.
* If the bug was a crash, the exact text that was printed out
when the crash occured.
* Further information such as stack traces may be useful, but
is not necessary. If you do send a stack trace, and the error
Patches
=======
Patches can be sent to nwanua@colorado.edu
Please include your name and email address in the README file for
you patch.
If the patch fixes a bug, it is usually a good idea to include
all the information described in "How to Report Bugs".
Nwanua Elumeze (nwanua@colorado.edu)