from the author:
"I started to write at the Reports module.
from a table, no filters, no sorts (yet) !
Of course, no prints ! Only fields in output report (no labels, lines or
rectangles)!
I am working now at region resizing (page header, footer, detail, etc)
Reports will be generated as Postscript file!
stay close ..."
systems because I've made an error in the original ePerl 2.2.9 tarball (under
my FreeBSD boxes it worked, because there a /sw/bin/perl exists). I've now
fixed it for 2.2.10 and now the ports is again ok. At least I hope that it is
ok now again... ;_)
I know some people are working on splitting this port up, so this
is just a stop-gap solution until then.
Also remove the extra "\" at the end of the last master site.
them however (newsgroups.patch) is relative to a different directory
than the others so I've left it out for the time being. I can fix this
by duplicating the entire do-patch clause from bsd.port.mk into the
Makefile so that different -d switches can be given for different patch
files, but that's overkill. Also, fix the md5 file as Satoshi pointed out.
Update to version 0.70
From his announcement:
> PgAccess v0.70 handles now user defined forms and scripts!
>
> Manipulating forms, PgAccess could be enhanced by the user in order to
> generate new applications.
> The powerfull scripting feature inherited from Tcl/Tk, the native
> environment of PgAccess, allow users to define and use new procedures,
> libraries and even call "system" procedures that I have been used
> writting PgAccess. I would say that PgAccess will be able to accept
> "plugin" modules in order to make him more powerfull. It will make him
> just a "shell" who will set up only a "working environment" for newly
> developed applications!!!!
>
> More information and some examples you will find at
> http://www.flex.ro/pgaccess/pga-rad.html
>
> Once more, I would like to thank you folks for giving me PostgreSQL and
> Visual Tcl, and hoping that PgAcces would help making them more popular!
The documentation-minded may wish to mention this in the
handbook somewhere.
PR: ports/5279
Submitted by: Ian Vaudrey [3]Ian Vaudrey <i.vaudrey@bigfoot.com>
When running as root everything is fine.
When running as normal user, it doesn't find the plugin
when clicking Help->About Plugins
Therefore I marked the port BROKEN for now. please report
your experiences to me, I only can test it under -current and
I'm not sure if I trapped into a -current or config problem.
The FAQ tells to explicitely set NPX_PLUGIN_PATH when
installing netscape in a non standard place, but
/usr/local/lib/netscape/plugins is a standard place and even
if I modify /usr/local/bin/netscape, it doesn't find any plugin.
Even not the nullplugin, which is pretty standard I think ...
Please help me out here, if you have some spare time.
OpenBSD and FreeBSD now both use rresvport. This is a nop for
FreeBSD, but for OpenBSD this picks random port numbers.
Submitted by: deraadt@cvs.openbsd.org
