DEPENDS+= ghostscript-[6-9]*:../../print/ghostscript
and packages needing just any ghostscript binary use
DEPENDS+= ghostscript{,-nox11}-[6-9]*:../../print/ghostscript
-- Fixed a "Status: Down" machine name output problem in machine
parseable logs found by Alek O. Komarnitsky ( alek (at) ast.lmco.com )
-- Took some wierd files out of the doc directory (cd, grep , vi, and
.swp)
-- Fixed some typos found by Thomas Klausner ( wiz (at)
danbala.ifoer.tuwien.ac.at )
Fixes PR 10054 by Reinoud Koornstra (reinoud@ibbnet.org).
Only package left to do is jakarta, which will be done as part of an upgrade
to jakarta-3.1 tonight or tomorrow.
Also, look for a swing package to be committed tonight or tomorrow -- if we
can't have JDK 1.2 right now, we can at least have swing...
BTW, the JServ jar does not go in ${PREFIX}/lib/java as it is a private
implementation of the interfaces from jsdk.jar and should not be used
directly. Should it turn out that packages are using it directly, it
will be moved.
While here, don't install the whole jsdk20 environment, as this is an older
version, and is generally useful only in order to get the jsdk20 jar file
for building jserv. This means we no longer install the bin/servletrunner
test harness, and we no longer install the jsdk source.
Users interested in these would be better off looking at the current jsdk
(pkgsrc/www/jakarta-tomcat), or jsdk2.1, which does not currently have
a package, but is at least rather less obsolete...
jserv will be adapted to use the new paths for this in a separate commit,
in a few minutes.
* binaries which are not JVM dependent go in ${PREFIX}/bin
* jar/zip/etc files for use by java programs go in
${PREFIX}/lib/java
* examples for java packages go in ${PREFIX}/share/examples/java
* documentation for java packages go in ${PREFIX}/share/doc/java
JVMs go in their own directories, right now ${PREFIX}/{java,kaffe}, which
is necessary so that multiple JVMs can be installed concurrently, and so
that the miriad packages which count on ${JAVA_HOME} pointing to a JVM
install will DTRT.
Most java packages already use something similar or can be adapted easily.
Java packages such as Jakarta with large amounts of private java will need
to be addressed separately.
more. Change since version 1.0.1i:
- heavily improved IMAP support (thanks to Brandon Long
and Brendan Cully for their work),
- support for using IMAP over SSL (thanks to Tommi
Kommulainen),
- a completely changed interface for configuring mutt's
PGP support. It's now format-based, and much more
flexible than it used to be in the past.
- a split of the old edit-message command into
resend-message and edit-message. While the former gives
you what could be described as "recall from arbitrary
folders", the latter can be used to low-level modify
messages.
- the weeding paradigma has changed. Instead of options
controlling weeding behaviour for all kinds of purposes,
there is one global $weed option which is toggled when
you use what used to be known as display-headers (now
display-toggle-weed). That is, you have some kind of
"WYSIWYG" support with weeding.
- we have a muttrc (5) manual page now, and it's even
up-to-date.
- you can better control your messages' header and
envelope from headers
- the message commands on the attachment menu have been
rewritten. Just try replying to an attachment, and
you'll see what happens. ;-)
- mailing list support has changed. You may wish to
rename your "lists" commands to "subscribe". But please
read README.UPGRADE before!
- Bug fixes of all sorts.
Changes from 1.0:
- A few bug Fixes.
- lenIV=-1 is now handled. According to an undocumented Adobe convention
lenIV=-1 indicates suppressing of charstring encryption.
- Patches to compile t1lib und MS Visual C++ 6.0. In case something goes
wrong, please contact Nakano Hideo (hideo@mb.infoeddy.ne.jp).
This version is considered to be release quality, but I'm putting
this under lynx-current pending integration of ipv6 support. Also,
socks is said to be broken in this release.
Add a hook to use "ncurses" for the screen library -- currently
the only way to get color-style support, or "curses" -- for the
day when NetBSD curses supports color. "slang" remains the default.
