[naviserver-devel] Release Candidate for NaviServer 4.99.16
Dear all,
On [1] is a release candidate for NaviServer 4.99.16. Below is a -
preliminary -
summary of the changes since the last release. If you have urgent changes
for this release, please get in touch with me. If everything goes well,
the release
should follow early next week. Please test if possible.
all the best
-gn
[1] https://sourceforge.net/projects/naviserver/files/naviserver/4.99.16/
===
NaviServer 4.99.16rc, released 2017-XX-XX
===
344 files changed, 16011 insertions(+), 10077 deletions(-)
New Features:
-
- ns_cache improvements:
* Allow runtime reaction and re-configuration of caches
(e.g. grow/shrink a cache via new cmd ns_cache_configure)
* Added cache transaction semantics
Background: when ns_cache_* commands are used within a database
transaction (e.g. in OpenACS), it might occur, that partial
results of the transaction are cached before the transaction is
committed. When the transaction is rolled back, invalid values
might be kept in the stack leading to erroneous and hard to
debug behavior. Furthermore, information about changes might
leak into other concurrent threads via the cache, even before
the transaction is committed.
The new cache transaction semantics is implemented via the three
commands
- ns_cache_transaction_begin
- ns_cache_transaction_commit
- ns_cache_transaction_rollback
When no ns_cache_transaction* commands are used, the behavior is
exactly as before.
When ns_cache_transaction* commands are in use, the following
functionalities become available
- The ability to rollback of the values since the matching
ns_cache_transaction_begin
- Isolation of behavior: cached values from incomplete cache
transactions are just visible from the current thread, but
not from other threads.
- Nesting: transactions can be nested
(up to a compile time constant, per default: 16)
- Introspection: the statistics about cache commits and
rollbacks are included in the cache statistics.
* Support caches larger than 2GB
* Summary of new ns_cache* commands
. ns_cache_configure to change cache parameters at runtime
. ns_cache_exists: This is is more than an order of
magnitude faster than [expr {"foo" in [ns_cache_names]]
. ns_cache_transaction_begin
. ns_cache_transaction_commit
. ns_cache_transaction_rollback
- Virtual server improvements
Make mapping of host entries in the virtual server definition more
intelligent to avoid newbie gotchas and hard to find
mis-configurations (entries in e.g. nssock/servers)
a) add automatically an entry with the port, when non is given
b) complain, when driver is not listening on the specified port
c) add automatically an entry without the port, when the driver
listening on the default port.
Old configurations (doing a-z manually) should continue to work
- Improved integration of NaviServer with e.g service files (systemd):
When the server is starting in a forking mode, return a non-zero
return code, when initialization of the server went wrong (e.g.
error in the config file)
- nsdb:
provide interface for obtaining session_ids. When implementing
e.g. prepared statements over the nsdbpg driver, the prepared
statement is just valid for one session. by providing the
session_id on the Tcl layer, prepared statements can be provided
selectively on the Tcl level.
- https:
* Support OpenSSL 1.1.0
* Improved support for ancient versions of OpenSSL (e.g. in CentOS 5.0)
* Added support for for client side Server Name Indication (SNI)
* Report attempted TLS handshakes on plain connections to error.log
- nscgi: new config parameter "allowstaticresources"
New parameter "allowstaticresources": provide control on whether
static resources can be delivered from a cgi-bin directory.
Background: when cgi scripts are called from a cgi-bin directory
without an explicit extension mapping to a script interpreter
(e.g. Perl, Bash, ...) the script has to be set executable. If
this is not the case, the cgi-script is delivered in source code,
which might reveal unwanted information. The reason for this
behavior was, that one can so deliver also static resources
(e.g. images) from a cgi- bin directory. Now this behavior con be
controlled with the configure parameter "allowstaticresources",
which is by default off. If an application depends on this
behavior, please turn it on in the config file (in the nscgi
section).
- nsproxy:
New subcommand "ns_proxy stats" to provide usage and runtime
statistics per nsproxy pool.
- logging:
* Better err
[naviserver-devel] Release candidate for NaviServer 4.99.14
Dear friends of NaviServer,
on sourceforge is a release candidate for NaviServer 4.99.14 (see [1]).
The version fixes essentially a few new and a few old bugs and continues
the ongoing code cleanup process. Also the portability is improved
(FreeBSD, OmniOS) and ns_connchan was stress-tested via the new
revproxy module and received several updates.
If everything goes well, the release should follow next week.
Please test if possible. Below are the changes since 4.99.14:
best regards
-gustaf
[1] https://sourceforge.net/projects/naviserver/files/naviserver/4.99.14/
===
NaviServer 4.99.14, released 2016-11-XX
===
66 files changed, 2391 insertions(+), 1327 deletions(-)
New Features:
* Added statistics for "trace times": i.e. the time spent in a
connection thread after the main request was executed, for running
post filters, server traces (e.g. writing access.log) and
cleanups. The statistic results are included in [ns_server
stats].
* Improved compatibility with FreeBSD and OminOS (Solaris).
* Added module "revproxy" for implementing a reverse proxy based
on ns_connchan (working as well for proxying WebSockets).
Performance Improvements:
* Added new config flag "concurrentinterpcreate" to "ns/parameters"
to allow optionally concurrent creations of Tcl interpreters.
Concurrent creations of tcl interpreters were a problem with Tcl
8.5, but seems to work with Tcl 8.6. Per default, this feature is
turned off.
* Don't update interp in "ns_ictl cleanup", when no defer callbacks
were executed.
Bug Fixes:
* ns_connchan improvements:
- Handle potential race condition between ns_connchan and socket
callbacks during shutdown
- Make sure, channel is writable before we are writing to it
- Add support for partial write operations ("ns_connchan write"
and "ns_connchan open")
- Provide more detailed error messages
- Allow callback changes without invoking socket-shutdown
machinery
* Make sure, the tests are running with expected locale and
encoding (fixed a problem on FreeBSD)
* Fix bug #77 (potential crash during ns_mktemp, strdup()
vs. ns_strdup(), introduced in 4.99.13, reported by
Patrick Heissenberger)
* Collect statistics before traces are run (i.e. before
access.log is written); this fixes a bug reported by
David Osborne.
* In HTTP client requests, don't start urls with "//" under certain
conditions
* Keep internally convention, that stored request lines do not end
with crlf to avoid unneeded tests
* Don't "roll away" log file from stderr, when nsd was started with
"-c" or "-f" flags
* Don't complain about uncorking, when user has already closed the
connection
* Make windows variant of ns_mkstemp() more compatible with unix/mac
(remove _O_TEMPORARY flag)
* Use datatype "int" for parameters passed with Ns_ObjvBool (rather
than bool, which causes invalid values on gcc 4.8.4 (Ubuntu
4.8.4-2ubuntu1~14.04.3))
* Fix several bugs in keylist
Documentation improvements:
* doc/src/naviserver/ns_connchan.man:
- Added documentation for "ns_connchan open"
- Clarified format in which timeouts can be specified
- document new flags
* doc/src/manual/admin-tuning.man:
- Added documentation of "ns/parameter" option "concurrentinterpcreate"
* doc/src/manual/admin-maintenance.man:
- Added section with sample configuration for systemd
* doc/src/naviserver/ns_mktemp.man:
- Improved function, explain deprecation state of c-library function,
* General overhaul of the contrib/example scripts
contrib/examples/index.adp, contrib/examples/upload.tcl,
contrib/examples/writer.tcl
* Various small documentation improvements.
* Improved sample config files.
Tcl API Changes:
* ns_connchan:
Added flag "-version" to "ns_connchan open" to specify
HTTP version (default 1.0)
C API Changes:
Incompatible API Changes:
Configuration Changes:
* Improved output of "make help"
* Don't throw error message, when doing an install from a bitbucket
checkout and no documentation was generated locally.
Command Line Changes:
* improve usefulness of "nsd -c": in case the environment variable
NAVISERVER is not set, and bin/init.tcl is not found under the
running binary, fall-back to the configured install directory as
"home".
Code Changes:
* Extended regression test
* Keylists:
- Added new testset for keylists
- fixed several bugs
- use naviserver memory management
- prefer Tcl_Objs over string based interface
* Improved source code documentation
* Turn ns_tmpnam into a proc and get rid of call to deprecated C
library function tmpnam()
* Added preprocessor variable NS_NAVISERVER to p
[naviserver-devel] Release candidate for NaviServer 4.99.13
Dear friends of NaviServer, on sourceforge is a release candidate for NaviServer 4.99.13 (see [1]). The version fixes essentially two relatively fresh bugs and continues the ongoing code cleanup process. For example, NaviServer compiles now clean with the type conversion, signed-unsigned comparisons etc. flags turned on in clang/gcc, which are discussed in the interesting paper [2] published recently at at CCS’16, where the authors identified related security flaws in prominent software such as the Linux Kernel, Chromium, boost, libarchive and zlib. If everything goes well, the release should follow end of this week. Please test if possible. Below are the changes since 4.99.12: best regards -gustaf [1] https://sourceforge.net/projects/naviserver/files/naviserver/4.99.13/ [2] https://www.tu-braunschweig.de/Medien-DB/sec/pubs/2016-ccs.pdf === NaviServer 4.99.13, released 2016-XX-XX === 137 files changed, 2808 insertions(+), 1913 deletions(-) New Features: - New Tcl functions: * ns_parseurl /url/ Parse the provided URL into its parts and returns these in the form of a Tcl dict. The function supports IP-literal notation as specified in RFC 3986. * ns_absoluteurl /incompleteurl/ /baseurl/ Construct a completed URL from a incomplete (e.g. relative) URL by taking as many parts as possible from the provided base URL. - ns_striphtml: The function honors now numeric entities between 33 and 255 instead of ignoring it. - New configure option for error.log: "logrollfmt", which can be specified in (section ns/parameters). This option has the same interpretation as already provided for access log and provides timestamp based log file naming. This option can reduce back-up demands for large error.logs significantly (since the names are stable) and increases the orthogonality of options (in respect to access.logs). - Ns_ParseUrl(): add support for protocol agnostic URLs (starting with two slashes as defined in RFC 3986). - ns_deletecookie: mark deleted cookie as non-scriptable to improve ratings on security scanners. Performance Improvements: Bug Fixes: - Fix for [naviserver:bugs] #76: ns_configsections returned only one section (bug introduced in 4.99.12). - Fix URL parser in Ns_ParseUrl(), could return incorrect results when it received an URL in IP-literal notation (bug introduced in 4.99.11). - Fix for potentially incorrect mime-types in fastpath, when static gzip is activated. The mime type was incorrectly set to application/gzip, when the static gzipped file was returned. This bug was introduced in 4.99.12, many thanks to David Osborne for reporting). Documentation improvements: - Documenting new functions - Several small cleanups - Improved sample config files Tcl API Changes: C API Changes: Incompatible API Changes: Configuration Changes: Command Line Changes: Code Changes: - Extended regression test - Improved source code documentation - C-Code cleanup: * Removed all implicit type-conversions, signed/unsigned comparisons as flagged by the following gcc/clang flags (ensure cleanness on 64bit) -Wconversion -Wsign-conversion -Wfloat-conversion -Wsign-compare * Reduced number of return statement before end of function * Reduced variable scopes * Remove calls to Tcl functions which are deprecated/ going to be deprecated by Tcl. Code can be compiled now with -DTCL_NO_DEPRECATED * Converted all remaining Tcl_CmdProc to Tcl_ObjCmdProc NsTclAdpStatsCmd-> NsTclAdpStatsObjCmd NsTclCrashCmd -> NsTclCrashObjCmd NsTclHrefsCmd -> NsTclHrefsObjCmd NsTclLibraryCmd -> NsTclLibraryObjCmd NsTclMkTempCmd -> NsTclMkTempObjCmd NsTclParseHeaderCmd -> NsTclParseHeaderObjCmd NsTclQuoteHtmlCmd -> NsTclQuoteHtmlObjCmd NsTclStripHtmlCmd -> NsTclStripHtmlObjCmd - Tcl-Code * tcl/aolserver-openacs.tcl: Register delete trace to run nsf::finalize in a safe state (before any other c-based finalize handler are fired) * regression test: Replaced Tcl "eval" by expand operator -- Check out the vibrant tech community on one of the world's most engaging tech sites, SlashDot.org! http://sdm.link/slashdot ___ naviserver-devel mailing list naviserver-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/naviserver-devel
[naviserver-devel] release candidate for NaviServer 4.99.12
Dear friends of NaviServer, on sourceforge is a release candidate for NaviServer 4.99.12. If everything goes well, the release should follow end of this week. Below are the changes since 4.99.11: best regards -gustaf === NaviServer 4.99.12, released 2016-08-XX === 195 files changed, 19904 insertions(+), 13118 deletions(-) New Features: * OpenSSL support integrated with NaviServer core - ns_http can handle now http and https urls - added backward_compatibility stub for ns_ssl - added configure switch --with-openssl?=path? * Improved crypto support (through OpenSSL) New commands: - ns_hmac - ns_md (generalization of ns_md4 and ns_sha1, but supports by default 14 different digest algorithms) - ns_hotp (one-time passwords as defined in RFC 4226) - ns_totp (time-based one-time passwords as defined in RFC 6238) StartTLS support (contributed by Constantin Șerban-Rădoi) - "ns_sendmail" is now able to connect to servers via StartTLS (requires the Tcl "tls" package, since ns_sendmail is implemented in Tcl) - Client and server support for StartTLS in the nssmtpd module. * New Command "ns_rlimit" to get/set various resource limits from the operating system. A typical use case for this command is to query or set e.g. the core size via the NaviServer startup file or to change it at runtime in a syntax independent from the naming and conventions in the various startup scripts (e.g. upstart, systemd, ...). This is e.g. useful when a core dump should be created from the running state (e.g. in combination with the "ns_crash" command). * Improvements for "ns_connchan": - Supports now client functionality via ns_connchan open ... (works for http:// and https:// URLs) - New subcommand "ns_connchan exists /channel/" - Added runtime switchable debug severity "Debug(connchan)" Performance Improvements: Bug Fixes: * Fix ns_set management of headers (which was broken since the introduction of the leftover management when requests are pipelined in 4.99.11). The problem was that the "static" ns_set for headers is was freed to early in the pipelined case. * Fix for a serious bug in cookie management which could lead to false positives in ns_getcookie: - Previous versions of NaviServer searched the "Cookie" and "Set-Cookie" header files for a string "NAME=" and returned the value provided after this string, when found. - However, the "Cookie" and "Set-Cookie" header fields have contents in a different a different syntax (see https://tools.ietf.org/html/rfc6265 section 4.1.1 vs. 4.2.1), such as e.g. Cookie: cookie1="value1"; cookie2="value2"; style=null; ... Set-Cookie: cookie1="new- value"; Expires=Fri, 01-Jan-2035 01:00:00 GMT; Path=/; HttpOnly - Therefore, searching in the "Cookie" header field e.g. for a cookie named "tyle" lead to a success as well as a search in "Set-Cookies" for e.g. a cookie named "Expires". * Improved handling of erroneous requests (some where treated as HTTP/0.9 requests before, leading to strange behavior/error messages). * Fix potential memory leak for "ns_mutex eval" * Long standing bug when exiting "make test" should be fixed by now. The problem was that the the Tcl exit handler was kicking in when the end-of file was reached, interfering with the NaviServer shutdown steps. * Improved portability for *BSD systems and recent Windows build environments (e.g. Visual Studio 2015) Documentation improvements: * New man pages for ns_hmac, hs_md, ns_hotp, ns_totp * Various man pages updated/improved * Improved sample config files C API Changes: * Introduction of Ns_ReturnCode: use an enumeration type instead of preprocessor based constants + int. The change revealed several places, where NS_OK/NS_ERROR and TCL_OK/TCL_ERROR were intermixed. * New functions - Ns_GetBinaryString() to obtain from a Tcl_Obj the binary representation if available, otherwise the string representation. - Ns_SetRecreate() which is a combination of a create and a move operation, but avoiding malloc operations on all keys/values. - Ns_DStringAppendTime() to ease uniform printing of Ns_Time structs into DStrings - Ns_SubcmdObjv(): New infrastructure support for commands with subcommands: instead of long switch statements with nested structures with often many returns, one can now register Tcl_ObjCmdProcs for subcommands in an Ns_SubCmdSpec structure. - New argv checkers Ns_ObjvUShort() and ObjvQueue() Configuration Changes: - added configure switch --with-openssl?=path?
Re: [naviserver-devel] Release
On Tue, Feb 10, 2009 at 1:04 AM, Ian Harding wrote: > Ah, I think I found it. Never mind my question. Hoping you found autogen.sh... (Only needed when checking out from the repository to bootstrap the automake stuff). -- Create and Deploy Rich Internet Apps outside the browser with Adobe(R)AIR(TM) software. With Adobe AIR, Ajax developers can use existing skills and code to build responsive, highly engaging applications that combine the power of local resources and data with the reach of the web. Download the Adobe AIR SDK and Ajax docs to start building applications today-http://p.sf.net/sfu/adobe-com ___ naviserver-devel mailing list naviserver-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/naviserver-devel
Re: [naviserver-devel] Release
Ah, I think I found it. Never mind my question. On Sat, May 12, 2007 at 12:43 PM, Stephen Deasey wrote: > You're not checking the tarball (which is what we distribute), you're > checking a CVS checkout. > > You need to: > > cvs export naviserver > cd naviserver > ./autogen.sh ... > make dist > cd /tmp > tar xzf ~/naviserver/naviserver-4.99.2.tar.gz > cd naviserver-4.99.2 > ./configure ... > make > make install > > So, it looks like 'make dist' is bust. > > > On 5/12/07, Vlad Seryakov wrote: >> CVS HEAD just got installed fine on my Linux, it was fine for a long >> time, must've been something with your checkout >> >> > Some install errors: >> > >> > make[1]: Leaving directory `/home/sd/tmp/naviserver-4.99.2/nsproxy' >> > cp: cannot stat `nsd-config.tcl': No such file or directory >> > chmod: cannot access `/tmp/ns/conf/#inst.19638#': No such file or directory >> > mv: cannot stat `/tmp/ns/conf/#inst.19638#': No such file or directory >> > cp: cannot stat `simple-config.tcl': No such file or directory >> > chmod: cannot access `/tmp/ns/conf/#inst.19652#': No such file or directory >> > mv: cannot stat `/tmp/ns/conf/#inst.19652#': No such file or directory >> > cp: cannot stat `index.adp': No such file or directory >> > chmod: cannot access `/tmp/ns/pages/#inst.19660#': No such file or >> > directory >> > mv: cannot stat `/tmp/ns/pages/#inst.19660#': No such file or directory >> > >> >> >> - >> This SF.net email is sponsored by DB2 Express >> Download DB2 Express C - the FREE version of DB2 express and take >> control of your XML. No limits. Just data. Click to get it now. >> http://sourceforge.net/powerbar/db2/ >> ___ >> naviserver-devel mailing list >> naviserver-devel@lists.sourceforge.net >> https://lists.sourceforge.net/lists/listinfo/naviserver-devel >> > > - > This SF.net email is sponsored by DB2 Express > Download DB2 Express C - the FREE version of DB2 express and take > control of your XML. No limits. Just data. Click to get it now. > http://sourceforge.net/powerbar/db2/ > ___ > naviserver-devel mailing list > naviserver-devel@lists.sourceforge.net > https://lists.sourceforge.net/lists/listinfo/naviserver-devel > -- Create and Deploy Rich Internet Apps outside the browser with Adobe(R)AIR(TM) software. With Adobe AIR, Ajax developers can use existing skills and code to build responsive, highly engaging applications that combine the power of local resources and data with the reach of the web. Download the Adobe AIR SDK and Ajax docs to start building applications today-http://p.sf.net/sfu/adobe-com ___ naviserver-devel mailing list naviserver-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/naviserver-devel
Re: [naviserver-devel] Release
On 8/3/07, Stephen Deasey <[EMAIL PROTECTED]> wrote:
> The *.test file are in utf-8, and are sourced by Tcl, and I think Tcl
> it's picking up the default encoding to use from the env. So no real
> surprise there. You'd expect encoding.test:1.1, which is completely
> defined within that file, to fail.
>
> But why are the ADP tests failing? The ADP's should be read off disk
> in the correct encoding (and they seem to be). Tracing through the
> rest of it, the server seems to be spitting out the correct bytes (I
> think).
>
> So it's down to the test harness itself. It does this:
>
> proc nstest_http {args} {
> ns_parseargs {
> {-encoding "utf-8"} ...
> } $args
>
> ...
>
> #
> # Force a specific encoding (utf-8 default).
> #
>
> fconfigure $rfd -encoding $encoding
> fconfigure $wfd -encoding $encoding
>
>
> Which looks fair enough to me.
>
> Why isn't this working?
Well, I'm reasonably happy this is not a bug in the server but some
cruftyness in the test harness.
If you were relying on environment variables to set the Tcl system
encoding before, you'll want to use the new
ns/server/$server:systemencoding parameter.
-
This SF.net email is sponsored by: Splunk Inc.
Still grepping through log files to find problems? Stop.
Now Search log events and configuration files using AJAX and a browser.
Download your FREE copy of Splunk now >> http://get.splunk.com/
___
naviserver-devel mailing list
naviserver-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/naviserver-devel
Re: [naviserver-devel] Release
The *.test file are in utf-8, and are sourced by Tcl, and I think Tcl
it's picking up the default encoding to use from the env. So no real
surprise there. You'd expect encoding.test:1.1, which is completely
defined within that file, to fail.
But why are the ADP tests failing? The ADP's should be read off disk
in the correct encoding (and they seem to be). Tracing through the
rest of it, the server seems to be spitting out the correct bytes (I
think).
So it's down to the test harness itself. It does this:
proc nstest_http {args} {
ns_parseargs {
{-encoding "utf-8"} ...
} $args
...
#
# Force a specific encoding (utf-8 default).
#
fconfigure $rfd -encoding $encoding
fconfigure $wfd -encoding $encoding
Which looks fair enough to me.
Why isn't this working?
On 8/3/07, Vlad Seryakov <[EMAIL PROTECTED]> wrote:
> I could have not correct environment, let me check with fresh install,
> it is happening everytime, we may put big fat warning in make tst to
> make sure it is running on fresh install :-)))
>
> Stephen Deasey wrote:
> > On 8/3/07, Vlad Seryakov <[EMAIL PROTECTED]> wrote:
> >> ... there are still errors in encoding tests.
> >>
> >> Stephen, i was quite busy lately and lost track, is it still broken or
> >> tests are just to up to date? The reason is, we cannot release with
> >> broken encoding support.
> >
> > Oh. I didn't know about this. Works for me.
> >
> > This fails though:
> >
> > LANG=en_US.iso-8859-1 make test TCLTESTARGS="-file encoding.test"
> >
> > (my default is UTF-8)
> >
> > I'll take a look...
> >
-
This SF.net email is sponsored by: Splunk Inc.
Still grepping through log files to find problems? Stop.
Now Search log events and configuration files using AJAX and a browser.
Download your FREE copy of Splunk now >> http://get.splunk.com/
___
naviserver-devel mailing list
naviserver-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/naviserver-devel
Re: [naviserver-devel] Release
I could have not correct environment, let me check with fresh install, it is happening everytime, we may put big fat warning in make tst to make sure it is running on fresh install :-))) Stephen Deasey wrote: > On 8/3/07, Vlad Seryakov <[EMAIL PROTECTED]> wrote: >> ... there are still errors in encoding tests. >> >> Stephen, i was quite busy lately and lost track, is it still broken or >> tests are just to up to date? The reason is, we cannot release with >> broken encoding support. > > Oh. I didn't know about this. Works for me. > > This fails though: > > LANG=en_US.iso-8859-1 make test TCLTESTARGS="-file encoding.test" > > (my default is UTF-8) > > I'll take a look... > > - > This SF.net email is sponsored by: Splunk Inc. > Still grepping through log files to find problems? Stop. > Now Search log events and configuration files using AJAX and a browser. > Download your FREE copy of Splunk now >> http://get.splunk.com/ > ___ > naviserver-devel mailing list > naviserver-devel@lists.sourceforge.net > https://lists.sourceforge.net/lists/listinfo/naviserver-devel > - This SF.net email is sponsored by: Splunk Inc. Still grepping through log files to find problems? Stop. Now Search log events and configuration files using AJAX and a browser. Download your FREE copy of Splunk now >> http://get.splunk.com/ ___ naviserver-devel mailing list naviserver-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/naviserver-devel
Re: [naviserver-devel] Release
On 8/3/07, Vlad Seryakov <[EMAIL PROTECTED]> wrote: > > ... there are still errors in encoding tests. > > Stephen, i was quite busy lately and lost track, is it still broken or > tests are just to up to date? The reason is, we cannot release with > broken encoding support. Oh. I didn't know about this. Works for me. This fails though: LANG=en_US.iso-8859-1 make test TCLTESTARGS="-file encoding.test" (my default is UTF-8) I'll take a look... - This SF.net email is sponsored by: Splunk Inc. Still grepping through log files to find problems? Stop. Now Search log events and configuration files using AJAX and a browser. Download your FREE copy of Splunk now >> http://get.splunk.com/ ___ naviserver-devel mailing list naviserver-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/naviserver-devel
[naviserver-devel] Release
OpenACS project is considering us for use along with AOlserver and i think this is very good timing for release. using CVS had may not be good thing for people to get introduced with the project. I noticed along with long-standing writer/spooler bug which i am responsible to fix (and i use writer all the time without problems, that's why so long delay) there are still errors in encoding tests. Stephen, i was quite busy lately and lost track, is it still broken or tests are just to up to date? The reason is, we cannot release with broken encoding support. - This SF.net email is sponsored by: Splunk Inc. Still grepping through log files to find problems? Stop. Now Search log events and configuration files using AJAX and a browser. Download your FREE copy of Splunk now >> http://get.splunk.com/ ___ naviserver-devel mailing list naviserver-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/naviserver-devel
Re: [naviserver-devel] Release
On Mon, 21 May 2007 10:59:09 -0400 Mike <[EMAIL PROTECTED]> wrote: > On 5/21/07, Bernd Eidenschink <[EMAIL PROTECTED]> wrote: > > > Just (dist-)compiled on an Ubuntu 7.04, tomorrow I'll give it a try on a > > > SuSE Enterprise Linux (all 32bit). > > > > tomorrow never dies... > > I just dist-compiled on the SuSE Enterprise and it was all smooth jazz. > > Anyone test on a FreeBSD box yet? The last time Zoran helped me try, > there were a couple of hickups, but we did resolve them. Just want to > make sure the changes made it back into the main tree. If someone > would like access to a FreeBSD machine, just send me a mail, and I'll > arrange it. On NetBSD I test it. It works like perfect, with WebDAV support. I wil test the compilations method on FreeBSD today. Feri - This SF.net email is sponsored by DB2 Express Download DB2 Express C - the FREE version of DB2 express and take control of your XML. No limits. Just data. Click to get it now. http://sourceforge.net/powerbar/db2/ ___ naviserver-devel mailing list naviserver-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/naviserver-devel
Re: [naviserver-devel] Release
On 5/21/07, Bernd Eidenschink <[EMAIL PROTECTED]> wrote: > > Just (dist-)compiled on an Ubuntu 7.04, tomorrow I'll give it a try on a > > SuSE Enterprise Linux (all 32bit). > > tomorrow never dies... > I just dist-compiled on the SuSE Enterprise and it was all smooth jazz. Anyone test on a FreeBSD box yet? The last time Zoran helped me try, there were a couple of hickups, but we did resolve them. Just want to make sure the changes made it back into the main tree. If someone would like access to a FreeBSD machine, just send me a mail, and I'll arrange it. - This SF.net email is sponsored by DB2 Express Download DB2 Express C - the FREE version of DB2 express and take control of your XML. No limits. Just data. Click to get it now. http://sourceforge.net/powerbar/db2/ ___ naviserver-devel mailing list naviserver-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/naviserver-devel
Re: [naviserver-devel] Release
> Just (dist-)compiled on an Ubuntu 7.04, tomorrow I'll give it a try on a > SuSE Enterprise Linux (all 32bit). tomorrow never dies... I just dist-compiled on the SuSE Enterprise and it was all smooth jazz. Bernd. - This SF.net email is sponsored by DB2 Express Download DB2 Express C - the FREE version of DB2 express and take control of your XML. No limits. Just data. Click to get it now. http://sourceforge.net/powerbar/db2/ ___ naviserver-devel mailing list naviserver-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/naviserver-devel
Re: [naviserver-devel] Release
Updated Bernd Eidenschink wrote: > Hi Vlad, Stephen, > > looks good! > > Just (dist-)compiled on an Ubuntu 7.04, tomorrow I'll give it a try on a > SuSE Enterprise Linux (all 32bit). > > One little thing, isn't the message: > "You can now run NaviServer by typing one of the commands below:" > too optimistic - in case you compile to /usr/local/, you > must be root; if you then try to use one of the three examples you have > to specify a non-privileged user and group - but then nslog throws a > 'Permission denied' for opening the access.log... > > E.g. we should add something like: > > "You can now run NaviServer by > a) replacing and with an existing non-privileged system > user and group you want the server to run as > b) making the log directory writable: > chgrp path/logs > chmod g+rwx path/logs > > Choose from one of the following commands:" > > >> fixed >> >> Stephen Deasey wrote: >>> You're not checking the tarball (which is what we distribute), you're >>> checking a CVS checkout. >>> >>> You need to: >>> >>> cvs export naviserver >>> cd naviserver >>> ./autogen.sh ... >>> make dist >>> cd /tmp >>> tar xzf ~/naviserver/naviserver-4.99.2.tar.gz >>> cd naviserver-4.99.2 >>> ./configure ... >>> make >>> make install > > _ > Der WEB.DE SmartSurfer hilft bis zu 70% Ihrer Onlinekosten zu sparen! > http://smartsurfer.web.de/?mc=100071&distributionid=0066 > > > - > This SF.net email is sponsored by DB2 Express > Download DB2 Express C - the FREE version of DB2 express and take > control of your XML. No limits. Just data. Click to get it now. > http://sourceforge.net/powerbar/db2/ > ___ > naviserver-devel mailing list > naviserver-devel@lists.sourceforge.net > https://lists.sourceforge.net/lists/listinfo/naviserver-devel > - This SF.net email is sponsored by DB2 Express Download DB2 Express C - the FREE version of DB2 express and take control of your XML. No limits. Just data. Click to get it now. http://sourceforge.net/powerbar/db2/ ___ naviserver-devel mailing list naviserver-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/naviserver-devel
Re: [naviserver-devel] Release
Hi Vlad, Stephen, looks good! Just (dist-)compiled on an Ubuntu 7.04, tomorrow I'll give it a try on a SuSE Enterprise Linux (all 32bit). One little thing, isn't the message: "You can now run NaviServer by typing one of the commands below:" too optimistic - in case you compile to /usr/local/, you must be root; if you then try to use one of the three examples you have to specify a non-privileged user and group - but then nslog throws a 'Permission denied' for opening the access.log... E.g. we should add something like: "You can now run NaviServer by a) replacing and with an existing non-privileged system user and group you want the server to run as b) making the log directory writable: chgrp path/logs chmod g+rwx path/logs Choose from one of the following commands:" > > fixed > > Stephen Deasey wrote: > > You're not checking the tarball (which is what we distribute), you're > > checking a CVS checkout. > > > > You need to: > > > > cvs export naviserver > > cd naviserver > > ./autogen.sh ... > > make dist > > cd /tmp > > tar xzf ~/naviserver/naviserver-4.99.2.tar.gz > > cd naviserver-4.99.2 > > ./configure ... > > make > > make install _ Der WEB.DE SmartSurfer hilft bis zu 70% Ihrer Onlinekosten zu sparen! http://smartsurfer.web.de/?mc=100071&distributionid=0066 - This SF.net email is sponsored by DB2 Express Download DB2 Express C - the FREE version of DB2 express and take control of your XML. No limits. Just data. Click to get it now. http://sourceforge.net/powerbar/db2/ ___ naviserver-devel mailing list naviserver-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/naviserver-devel
Re: [naviserver-devel] Release
fixed Stephen Deasey wrote: > You're not checking the tarball (which is what we distribute), you're > checking a CVS checkout. > > You need to: > > cvs export naviserver > cd naviserver > ./autogen.sh ... > make dist > cd /tmp > tar xzf ~/naviserver/naviserver-4.99.2.tar.gz > cd naviserver-4.99.2 > ./configure ... > make > make install > > So, it looks like 'make dist' is bust. > > > On 5/12/07, Vlad Seryakov <[EMAIL PROTECTED]> wrote: >> CVS HEAD just got installed fine on my Linux, it was fine for a long >> time, must've been something with your checkout >> >>> Some install errors: >>> >>> make[1]: Leaving directory `/home/sd/tmp/naviserver-4.99.2/nsproxy' >>> cp: cannot stat `nsd-config.tcl': No such file or directory >>> chmod: cannot access `/tmp/ns/conf/#inst.19638#': No such file or directory >>> mv: cannot stat `/tmp/ns/conf/#inst.19638#': No such file or directory >>> cp: cannot stat `simple-config.tcl': No such file or directory >>> chmod: cannot access `/tmp/ns/conf/#inst.19652#': No such file or directory >>> mv: cannot stat `/tmp/ns/conf/#inst.19652#': No such file or directory >>> cp: cannot stat `index.adp': No such file or directory >>> chmod: cannot access `/tmp/ns/pages/#inst.19660#': No such file or directory >>> mv: cannot stat `/tmp/ns/pages/#inst.19660#': No such file or directory >>> >> >> - >> This SF.net email is sponsored by DB2 Express >> Download DB2 Express C - the FREE version of DB2 express and take >> control of your XML. No limits. Just data. Click to get it now. >> http://sourceforge.net/powerbar/db2/ >> ___ >> naviserver-devel mailing list >> naviserver-devel@lists.sourceforge.net >> https://lists.sourceforge.net/lists/listinfo/naviserver-devel >> > > - > This SF.net email is sponsored by DB2 Express > Download DB2 Express C - the FREE version of DB2 express and take > control of your XML. No limits. Just data. Click to get it now. > http://sourceforge.net/powerbar/db2/ > ___ > naviserver-devel mailing list > naviserver-devel@lists.sourceforge.net > https://lists.sourceforge.net/lists/listinfo/naviserver-devel > - This SF.net email is sponsored by DB2 Express Download DB2 Express C - the FREE version of DB2 express and take control of your XML. No limits. Just data. Click to get it now. http://sourceforge.net/powerbar/db2/ ___ naviserver-devel mailing list naviserver-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/naviserver-devel
Re: [naviserver-devel] Release
You're not checking the tarball (which is what we distribute), you're checking a CVS checkout. You need to: cvs export naviserver cd naviserver ./autogen.sh ... make dist cd /tmp tar xzf ~/naviserver/naviserver-4.99.2.tar.gz cd naviserver-4.99.2 ./configure ... make make install So, it looks like 'make dist' is bust. On 5/12/07, Vlad Seryakov <[EMAIL PROTECTED]> wrote: > CVS HEAD just got installed fine on my Linux, it was fine for a long > time, must've been something with your checkout > > > Some install errors: > > > > make[1]: Leaving directory `/home/sd/tmp/naviserver-4.99.2/nsproxy' > > cp: cannot stat `nsd-config.tcl': No such file or directory > > chmod: cannot access `/tmp/ns/conf/#inst.19638#': No such file or directory > > mv: cannot stat `/tmp/ns/conf/#inst.19638#': No such file or directory > > cp: cannot stat `simple-config.tcl': No such file or directory > > chmod: cannot access `/tmp/ns/conf/#inst.19652#': No such file or directory > > mv: cannot stat `/tmp/ns/conf/#inst.19652#': No such file or directory > > cp: cannot stat `index.adp': No such file or directory > > chmod: cannot access `/tmp/ns/pages/#inst.19660#': No such file or directory > > mv: cannot stat `/tmp/ns/pages/#inst.19660#': No such file or directory > > > > > - > This SF.net email is sponsored by DB2 Express > Download DB2 Express C - the FREE version of DB2 express and take > control of your XML. No limits. Just data. Click to get it now. > http://sourceforge.net/powerbar/db2/ > ___ > naviserver-devel mailing list > naviserver-devel@lists.sourceforge.net > https://lists.sourceforge.net/lists/listinfo/naviserver-devel > - This SF.net email is sponsored by DB2 Express Download DB2 Express C - the FREE version of DB2 express and take control of your XML. No limits. Just data. Click to get it now. http://sourceforge.net/powerbar/db2/ ___ naviserver-devel mailing list naviserver-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/naviserver-devel
Re: [naviserver-devel] Release
CVS HEAD just got installed fine on my Linux, it was fine for a long time, must've been something with your checkout > Some install errors: > > make[1]: Leaving directory `/home/sd/tmp/naviserver-4.99.2/nsproxy' > cp: cannot stat `nsd-config.tcl': No such file or directory > chmod: cannot access `/tmp/ns/conf/#inst.19638#': No such file or directory > mv: cannot stat `/tmp/ns/conf/#inst.19638#': No such file or directory > cp: cannot stat `simple-config.tcl': No such file or directory > chmod: cannot access `/tmp/ns/conf/#inst.19652#': No such file or directory > mv: cannot stat `/tmp/ns/conf/#inst.19652#': No such file or directory > cp: cannot stat `index.adp': No such file or directory > chmod: cannot access `/tmp/ns/pages/#inst.19660#': No such file or directory > mv: cannot stat `/tmp/ns/pages/#inst.19660#': No such file or directory > - This SF.net email is sponsored by DB2 Express Download DB2 Express C - the FREE version of DB2 express and take control of your XML. No limits. Just data. Click to get it now. http://sourceforge.net/powerbar/db2/ ___ naviserver-devel mailing list naviserver-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/naviserver-devel
Re: [naviserver-devel] Release
Good stuff. i'll finalize install and config issues, i do not have 64bits systems so cannot check that Stephen Deasey wrote: > On 5/12/07, Vlad Seryakov <[EMAIL PROTECTED]> wrote: >> Can we publish release, no many features were added recently, it is stable? >> >> i am using it at my new work and it would be better to have last >> official release than last development snapshot only. Now it looks >> pretty much abandoned with our last release almost 2 years ago. > > > 4.99.1 was released 2006-02-04, so 'only' ~1 year ago, but yeah, we > should release another one... :-) > > There are are some things which are kind of broken, but they've been > so for a while so I guess we'll get to it when we get to it. Every > one is using CVS head anyway so we might as well call it what it is: a > release. > > > Now would be a great time to some final clean ups -- > > Has anyone built it on Windows lately? I'm sure we've added new source > files but I don't recall seeing any changes to the Windows build > stuff. > > Does it build and run OK for people on their weird platform of choice? > > I tried on ia64/linux on HP's build farm while trying out some > autoconf changes and it segfaults during early start up with an > alignment error. Maybe this is to do with the logging changes? Haven't > had a chance to look at this yet... > > Need to trawl backwards through the ChangeLog and see if there's > anything interesting that should be added to the NEWS file. > > Would be nice to fix up the sample-config.tcl, I think a lot of things > have changed. This is a lot easier to check now with a simple grep > -C3 Ns_Config *.c > > If anyone feels like making a final push with documentation, now would > be a good time. Even just consolidating some of the many single pages > into a group of related commands on one page makes a big difference, > IMHO. > > e.g. > http://www.crystalballinc.com/vlad/software/naviserver/files/mann/ns_atsignal.html > here the commands are arranged in the order they fire within the > lifetime of the server. > > Some build warnings: > > adpparse.c: In function 'NsAdpParse': > adpparse.c:219: warning: 'ae' may be used uninitialized in this function > adpparse.c:219: warning: 'as' may be used uninitialized in this function > adpparse.c:218: warning: 'script' may be used uninitialized in this function > adpparse.c:217: warning: 'tagPtr' may be used uninitialized in this function > tclhttp.c:36: warning: 'RCSID' defined but not used > > Some install errors: > > make[1]: Leaving directory `/home/sd/tmp/naviserver-4.99.2/nsproxy' > cp: cannot stat `nsd-config.tcl': No such file or directory > chmod: cannot access `/tmp/ns/conf/#inst.19638#': No such file or directory > mv: cannot stat `/tmp/ns/conf/#inst.19638#': No such file or directory > cp: cannot stat `simple-config.tcl': No such file or directory > chmod: cannot access `/tmp/ns/conf/#inst.19652#': No such file or directory > mv: cannot stat `/tmp/ns/conf/#inst.19652#': No such file or directory > cp: cannot stat `index.adp': No such file or directory > chmod: cannot access `/tmp/ns/pages/#inst.19660#': No such file or directory > mv: cannot stat `/tmp/ns/pages/#inst.19660#': No such file or directory > > > Should we give it a week or so for people to do what they need to do > and then aim for a release? > > > Here's a snapshot tarball for people to test. I'll update it as > updates enter CVS: > > http://naviserver.sourceforge.net/snapshots/naviserver-4.99.2.tar.gz > > - > This SF.net email is sponsored by DB2 Express > Download DB2 Express C - the FREE version of DB2 express and take > control of your XML. No limits. Just data. Click to get it now. > http://sourceforge.net/powerbar/db2/ > ___ > naviserver-devel mailing list > naviserver-devel@lists.sourceforge.net > https://lists.sourceforge.net/lists/listinfo/naviserver-devel > - This SF.net email is sponsored by DB2 Express Download DB2 Express C - the FREE version of DB2 express and take control of your XML. No limits. Just data. Click to get it now. http://sourceforge.net/powerbar/db2/ ___ naviserver-devel mailing list naviserver-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/naviserver-devel
Re: [naviserver-devel] Release
On 5/12/07, Vlad Seryakov <[EMAIL PROTECTED]> wrote: > Can we publish release, no many features were added recently, it is stable? > > i am using it at my new work and it would be better to have last > official release than last development snapshot only. Now it looks > pretty much abandoned with our last release almost 2 years ago. 4.99.1 was released 2006-02-04, so 'only' ~1 year ago, but yeah, we should release another one... :-) There are are some things which are kind of broken, but they've been so for a while so I guess we'll get to it when we get to it. Every one is using CVS head anyway so we might as well call it what it is: a release. Now would be a great time to some final clean ups -- Has anyone built it on Windows lately? I'm sure we've added new source files but I don't recall seeing any changes to the Windows build stuff. Does it build and run OK for people on their weird platform of choice? I tried on ia64/linux on HP's build farm while trying out some autoconf changes and it segfaults during early start up with an alignment error. Maybe this is to do with the logging changes? Haven't had a chance to look at this yet... Need to trawl backwards through the ChangeLog and see if there's anything interesting that should be added to the NEWS file. Would be nice to fix up the sample-config.tcl, I think a lot of things have changed. This is a lot easier to check now with a simple grep -C3 Ns_Config *.c If anyone feels like making a final push with documentation, now would be a good time. Even just consolidating some of the many single pages into a group of related commands on one page makes a big difference, IMHO. e.g. http://www.crystalballinc.com/vlad/software/naviserver/files/mann/ns_atsignal.html here the commands are arranged in the order they fire within the lifetime of the server. Some build warnings: adpparse.c: In function 'NsAdpParse': adpparse.c:219: warning: 'ae' may be used uninitialized in this function adpparse.c:219: warning: 'as' may be used uninitialized in this function adpparse.c:218: warning: 'script' may be used uninitialized in this function adpparse.c:217: warning: 'tagPtr' may be used uninitialized in this function tclhttp.c:36: warning: 'RCSID' defined but not used Some install errors: make[1]: Leaving directory `/home/sd/tmp/naviserver-4.99.2/nsproxy' cp: cannot stat `nsd-config.tcl': No such file or directory chmod: cannot access `/tmp/ns/conf/#inst.19638#': No such file or directory mv: cannot stat `/tmp/ns/conf/#inst.19638#': No such file or directory cp: cannot stat `simple-config.tcl': No such file or directory chmod: cannot access `/tmp/ns/conf/#inst.19652#': No such file or directory mv: cannot stat `/tmp/ns/conf/#inst.19652#': No such file or directory cp: cannot stat `index.adp': No such file or directory chmod: cannot access `/tmp/ns/pages/#inst.19660#': No such file or directory mv: cannot stat `/tmp/ns/pages/#inst.19660#': No such file or directory Should we give it a week or so for people to do what they need to do and then aim for a release? Here's a snapshot tarball for people to test. I'll update it as updates enter CVS: http://naviserver.sourceforge.net/snapshots/naviserver-4.99.2.tar.gz - This SF.net email is sponsored by DB2 Express Download DB2 Express C - the FREE version of DB2 express and take control of your XML. No limits. Just data. Click to get it now. http://sourceforge.net/powerbar/db2/ ___ naviserver-devel mailing list naviserver-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/naviserver-devel
[naviserver-devel] Release
Can we publish release, no many features were added recently, it is stable? i am using it at my new work and it would be better to have last official release than last development snapshot only. Now it looks pretty much abandoned with our last release almost 2 years ago. - This SF.net email is sponsored by DB2 Express Download DB2 Express C - the FREE version of DB2 express and take control of your XML. No limits. Just data. Click to get it now. http://sourceforge.net/powerbar/db2/ ___ naviserver-devel mailing list naviserver-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/naviserver-devel
[naviserver-devel] Release
Hi guys, if we want to make release this year, we need to finish docs, i just cant make myself to finish it:-(( We have these pages to replace example text, of course the rest of manuals desire to be better but at least they have something. ns_limits_get.man ns_limits_list.man ns_limits_register.man ns_limits_set.man ns_locationproc.man ns_moduleload.man ns_parseargs.man ns_purgefiles.man ns_register_fastpath.man ns_register_fasturl2file.man ns_register_proxy.man ns_register_url2file.man ns_serverrootproc.man ns_shortcut_filter.man ns_startcontent.man ns_unregister_adp.man ns_unregister_url2file.man ns_var.man -- Vlad Seryakov 571 262-8608 office [EMAIL PROTECTED] http://www.crystalballinc.com/vlad/
Re: [naviserver-devel] Release
Am 03.02.2006 um 02:49 schrieb Vlad Seryakov: Just as an idea, Zoran, when you are ready to release 4.99.1, it could be a good idea to make a release on freshmeat.net as well. Also, can we make modules subdir as a separate .tar.gz as well? I see no reason why not. For naviserver, we have a "make dist". Is there anything like that for the rest of the modules? I believe not. So, something like "make dist" for all modules you made would be a good thing. Cheers Zoran
[naviserver-devel] Release
Just as an idea, Zoran, when you are ready to release 4.99.1, it could be a good idea to make a release on freshmeat.net as well. Also, can we make modules subdir as a separate .tar.gz as well? -- Vlad Seryakov 571 262-8608 office [EMAIL PROTECTED] http://www.crystalballinc.com/vlad/
Re: [naviserver-devel] Release/Docs
> OTOH, have you ever looked at doctools?
Not too much, but as I read here:
http://wiki.tcl.tk/3054
the conversions should be easy:
dtp doc html your_manpage > your_manpage.html
dtp doc nroff your_manpage > your_manpage.n
dtp doc text your_manpage > your_manpage.txt
And seems there's also "latex" (and therefor PDF) and "wiki":
http://aspn.activestate.com/ASPN/docs/ActiveTcl/tcllib/doctools/doctools.html
So, if we use doctools, we only would need
a) An autogenerated step to generate html,nroff (and wiki)
b) (Auto)generate an index.html file to all generated single html pages (easy)
I don't know the output of the doctool->wiki conversion, if it creates
[Wiki-Links] automagically so that we have relations for free. But that does
not matter. We know our commands so we can regsub and create those relations.
If we start with Wiki, we can create a nice Documentation with easy
relations/links between the commands and documents. But the
wiki->nroff step does not exist, does it? There are these small little
nroff-gadgets like ".sp" ("Skip one line vertically") or markup for italics
for function parameters. We can only produce really nice nroff/groff, if we
have a really good Wiki template and always use it correctly. At least this
is my impression.
BTW: How do we fetch our documentation out of Wiki for autogeneration of
documentation? Maybe we take a database dump and one of us accesses it local?
Hm...not good. Or spidering it... No.
So, somehow, seems the doctools approach would be easier right now.
And no one will complain that documentation is not on Wiki, if documentation
is available! :-)
Bernd.
Re: [naviserver-devel] Release/Docs
Am 05.07.2005 um 09:25 schrieb Stephen Deasey: Maybe we should pick one C function and one Tcl command to document fully on the wiki, write some wiki macros to make it easy, then try converting it into whatever? Eh... It seems that this task is a real PITA! I think somebody could make a fortune by inventing easy to use collaborative doc system able to generate just a handful of formats: pdf, nroff, html. If I understand this correctly, writing wiki pages is also a task you have to learn (wiki markup). This is the same as with doctools. Difference: in wiki everybody can do this from the browser, whereas in doctools you'd have to do it off-line and in a text editor. Apart that it is appealing to be able to write it on-line and it seems trivial for bunch of people to do it "at the same time" I see no other pros for Wiki. Cons are important: no simple interface to cvs (docs are vital part of the server), lack of usable converters... It seems like a lot of hacking for me and a great time eater. OTOH, doctools are already supporting (almost) everything we need. The cons are: you must edit sources off-line. Just to be clear: I'm not trying to push doctools vs. wiki. I'm just not convinced that wiki will save us any time and trouble. I have a notion that doctools are less problematic and would bring us to the goal (of having decent html/nroff docs distributed with the server) faster. I can imagine the following: We divide and conquer... Since I have more experience with doctools than wiki, I will take a C-API and a Tcl-API call and write source of the doc in doctools. Then I will convert this to nroff, html and wiki format by means of the "dtp" processor from the tcllib. You or Bernd can take the Wiki part and examine what would it mean to write a converter that would emit something like people are accustomed to when hitting "man fcopy" or "man lindex" or "man Tcl_NewObj". Then we can share experience (and source-files). How does this sound?
Re: [naviserver-devel] Release/Docs
On 7/5/05, Zoran Vasiljevic <[EMAIL PROTECTED]> wrote:
>
> Am 05.07.2005 um 08:43 schrieb Stephen Deasey:
>
> > On 7/5/05, Zoran Vasiljevic <[EMAIL PROTECTED]> wrote:
> >
> >>
> >> Am 05.07.2005 um 02:36 schrieb Stephen Deasey:
> >>
> >>
> >>> http://naviserver.sf.net/wiki/index.php/User:Sdeasey
> >>>
> >>> Neato: templates! The wiki == nroff :-)
> >>>
> >>
> >> Excuse my ignorance, but: where is nroff?
> >>
> >
> >
> > I was exagerating, sorry. Templates... with args... macros...
> > nroff...
> >
> >
> > Still, where man.macros (oh, my, God) has:
> >
> > .OP cmdName dbName dbClass
> >
> > The wiki would have Template:OP, called as:
> >
> > {{OP:cmdName=X|dbName=Y|dbClass=Z}}
> >
> > Which could expand to whatever you like, including HTML comments to
> > aid converting back to nroff etc...
>
>
> Does this mean that converting from wiki format to nroff
> would be relatively trivial? IOW, I can invent just about
> any Tempate:OP were OP is whatever nroff will support, like
> .CE, .CS, .PP, .SH ?
>
> I do not know wiki enough to be able to make any decision,
> but if there is a way of writing it all in wiki and getting
> it converted to decent nroff (and html) without much fuss,
> then I'm all for it.
>
> OTOH, have you ever looked at doctools?
>
> Zoran
I really don't know what the best thing to do is. I can see plusses
and minuses either way. I personally I don't have a lot of use for
paper docs, but I know it's important to some people.
You can already get an XML page dump:
http://naviserver.sourceforge.net/wiki/index.php/Special:Export/User:Sdeasey
Kind of dissapointing, just a big blob of wiki-source. However, the
macros are preserved. So the problem basically becomes, can you write
a program which spiders the website and converts {{X:1|2|3}} into .X 1
2 3.
Maybe we should pick one C function and one Tcl command to document
fully on the wiki, write some wiki macros to make it easy, then try
converting it into whatever?
Re: [naviserver-devel] Release/Docs
Am 05.07.2005 um 08:43 schrieb Stephen Deasey:
On 7/5/05, Zoran Vasiljevic <[EMAIL PROTECTED]> wrote:
Am 05.07.2005 um 02:36 schrieb Stephen Deasey:
http://naviserver.sf.net/wiki/index.php/User:Sdeasey
Neato: templates! The wiki == nroff :-)
Excuse my ignorance, but: where is nroff?
I was exagerating, sorry. Templates... with args... macros...
nroff...
Still, where man.macros (oh, my, God) has:
.OP cmdName dbName dbClass
The wiki would have Template:OP, called as:
{{OP:cmdName=X|dbName=Y|dbClass=Z}}
Which could expand to whatever you like, including HTML comments to
aid converting back to nroff etc...
Does this mean that converting from wiki format to nroff
would be relatively trivial? IOW, I can invent just about
any Tempate:OP were OP is whatever nroff will support, like
.CE, .CS, .PP, .SH ?
I do not know wiki enough to be able to make any decision,
but if there is a way of writing it all in wiki and getting
it converted to decent nroff (and html) without much fuss,
then I'm all for it.
OTOH, have you ever looked at doctools?
Zoran
Re: [naviserver-devel] Release/Docs
On 7/5/05, Zoran Vasiljevic <[EMAIL PROTECTED]> wrote:
>
> Am 05.07.2005 um 02:36 schrieb Stephen Deasey:
>
> > http://naviserver.sf.net/wiki/index.php/User:Sdeasey
> >
> > Neato: templates! The wiki == nroff :-)
>
> Excuse my ignorance, but: where is nroff?
I was exagerating, sorry. Templates... with args... macros... nroff...
Still, where man.macros (oh, my, God) has:
.OP cmdName dbName dbClass
The wiki would have Template:OP, called as:
{{OP:cmdName=X|dbName=Y|dbClass=Z}}
Which could expand to whatever you like, including HTML comments to
aid converting back to nroff etc...
Re: [naviserver-devel] Release/Docs
Am 05.07.2005 um 02:36 schrieb Stephen Deasey: http://naviserver.sf.net/wiki/index.php/User:Sdeasey Neato: templates! The wiki == nroff :-) Excuse my ignorance, but: where is nroff?
Re: [naviserver-devel] Release/Docs
http://naviserver.sf.net/wiki/index.php/User:Sdeasey Neato: templates! The wiki == nroff :-) Categories look useful too. Unfortunately all page names have their initial letter bashed to upper case, and underscores are converted to spaces... :-(
Re: [naviserver-devel] Release/Docs
Don't know if this is useful: http://hula-project.org/Wiki_Conversion Our idea is that there be a script on the wiki server that autogenerates PDFs of the admin guide, the user guide, and any other large-scale documentation, suitable for printing and binding and admiring and cherishing forever and ever. -- Nat Friedman
Re: [naviserver-devel] Release/Docs
Am 04.07.2005 um 16:45 schrieb Bernd Eidenschink: This way or another, it seems that if we'd have a wiki->html and wiki->nroff converters at hand, we could trash doctools... But I do not know if any of those already exists. OK, the wiki->html should already be there, otherwise wiki would not work ;-) But, what about wiki->nroff ? Hm, the existing nroff docs could be transformed like here: http://naviserver.sourceforge.net/wiki/index.php/ Template:Documentation_template I used the script that is found under the link "hack" at the end. (It's a hack. It's a hack.) The way back from wiki->nroff could be, depending on the nroff quality, more easy, if we use an easy and fresh Wiki document (and make use of standard HTML-Comments for better parsing). But it always would be unorthodox. :-) I see this really pragmatic: *I* would not like to invent the wheel. If there is some good quality wiki->nroff, wiki->html, wiki->(whatever) this would be the way to go: write all in Wiki and get it converted to other stuff. This is very appealing. If not, but somebody (you?) could write working converters for at least html and nroff conversion, I'd be happy to use them and would also opt to write source docs in wiki. Ideal would be a tclsh app I could hit like wiki2html source.wiki (would produce source.html in the current dir) wiki2nroff source.wiki (would produce source.nroff in the current dir) If not, I'd use doctools for already given reasons. It can't be that bad considering that all of tcllib modules are documented with doctools (with some notable deficiencies in documenting C-code as I already mentioned). Zoran
Re: [naviserver-devel] Release/Docs
> This way or another, it seems that if we'd have a wiki->html and > wiki->nroff converters at hand, we could trash doctools... But I > do not know if any of those already exists. OK, the wiki->html > should already be there, otherwise wiki would not work ;-) > But, what about wiki->nroff ? Hm, the existing nroff docs could be transformed like here: http://naviserver.sourceforge.net/wiki/index.php/Template:Documentation_template I used the script that is found under the link "hack" at the end. (It's a hack. It's a hack.) The way back from wiki->nroff could be, depending on the nroff quality, more easy, if we use an easy and fresh Wiki document (and make use of standard HTML-Comments for better parsing). But it always would be unorthodox. :-)
Re: [naviserver-devel] Release/Docs
Am 04.07.2005 um 10:14 schrieb Bernd Eidenschink:
than one C-API call. To get an idea, install Tcl and make:
man Tcl_FSStat
and you will see that the *entire* Tcl-VFS API is documented in
one single man-page.
ok, see. would be handy.
Watch! Although handy, it is pretty inflexible.
As an exercise, imagine you'd like to use Tcl_AllocStatBuf call.
Now, you naively go and "man Tcl_AllocStatBuf". You'd like to
get call signature and parameter description, but you also want
to look at what the call is really doing. Given the current state,
this is all but user-friendly and effective.
In order to understand what I mean, please do try "man Tcl_AllocStatBuf"
and judge by yourself...
Personally, I find it very annoying and ineffective.
Wiki seems very nice for collaborative work but I do not
know if there is a wiki->doctools converter (doctools->wiki there
is).
If we start hacking wiki, how would you convert this into some
other format?
Depends on what we need for doctools, or generally for documentation.
Example:
All Headings like NAME,SYNOPSIS,DESCRIPTION,EXAMPLES,SEE
ALSO,KEYWORDS are
representated the same in the wiki, e.g. a third-level-heading:
=== SEE ALSO ===
Other "markup" like bold or underline is also easy parseable
('''bold''').
"Examples" start with one or more whitespace on a line.
So I think it should be very easy to hack a convert, as the
structure is
always the same. Like this stupid hack:
http://naviserver.sourceforge.net/wiki/index.php/News2wiki.tcl
But, as the devil is in the details, maybe you send me a doctool-
document in
the form that you can imagine as a template for NaviServer, and I
take a look
at how complex it is to write a small converter script.
OK. I will prepare a doctool for a one ns_xyz and Ns_XYZ() (both Tcl
and C api).
You must install tcllib and there you will have a dtp utility which will
translate this in wiki or html or nroff for you.
If it turns out to be simple to write a wiki->doctools converter then
I'm all
for it. Then we'd use wiki to fill-in the content, use the translator to
generate doctools pages, then cvs-import those, then generate html/nroff
offline docs during installation. Ideally, the wiki->doctools should be
somehow automated.
Hm and what if we'd have a wiki->nroff and wiki->html off-line
converters? Than we'd have the sources of docs in native wiki format
and check-in those in CVS. During the "make install" we'd hit the
apropriate converter and generate html/nroff on the fly? Or we can
pre-format nroff/html and check-in those... ??
This way or another, it seems that if we'd have a wiki->html and
wiki->nroff converters at hand, we could trash doctools... But I
do not know if any of those already exists. OK, the wiki->html
should already be there, otherwise wiki would not work ;-)
But, what about wiki->nroff ?
The AS project started this and I do not see any moves
there. The wiki-entered stuff is still there and nobody cares to
get it into the CVS or get it translated to other off-line reading
(man, html, pdf, etc) ?
Thats true. I think the effort stopped at the very beginning or
halfway. But
if only we had it in the Wiki! The problem is that writing
documentation
sucks, not writing the converter :-)))
But yet, having a good framework in place would actually lower the
barrier of having to start to write actually.
Ok. But we should have a complete list for C and TCL to know whats
missing or
when we are finished.
If we manage to get Wiki-based thing, than all is already in-place,
right?
I started with TCL, but the list is not perfect:
http://naviserver.sourceforge.net/wiki/index.php/Examples:Commands
The problems with the list is that you need to update yet-another-thing.
I think that tagging the CVS now with 4.99.0 is perfectly OK as it
would
identify a body in CVS which is fixed and against which we can file
bugs.
Ok, so we tag it after the macro insertion (or whatever solution)
for the
range headers?
I would suggest so.
Zoran
Re: [naviserver-devel] Release/Docs
> than one C-API call. To get an idea, install Tcl and make:
>
>man Tcl_FSStat
>
> and you will see that the *entire* Tcl-VFS API is documented in
> one single man-page.
ok, see. would be handy.
> Wiki seems very nice for collaborative work but I do not
> know if there is a wiki->doctools converter (doctools->wiki there is).
> If we start hacking wiki, how would you convert this into some
> other format?
Depends on what we need for doctools, or generally for documentation.
Example:
All Headings like NAME,SYNOPSIS,DESCRIPTION,EXAMPLES,SEE ALSO,KEYWORDS are
representated the same in the wiki, e.g. a third-level-heading:
=== SEE ALSO ===
Other "markup" like bold or underline is also easy parseable ('''bold''').
"Examples" start with one or more whitespace on a line.
So I think it should be very easy to hack a convert, as the structure is
always the same. Like this stupid hack:
http://naviserver.sourceforge.net/wiki/index.php/News2wiki.tcl
But, as the devil is in the details, maybe you send me a doctool-document in
the form that you can imagine as a template for NaviServer, and I take a look
at how complex it is to write a small converter script.
> The AS project started this and I do not see any moves
> there. The wiki-entered stuff is still there and nobody cares to
> get it into the CVS or get it translated to other off-line reading
> (man, html, pdf, etc) ?
Thats true. I think the effort stopped at the very beginning or halfway. But
if only we had it in the Wiki! The problem is that writing documentation
sucks, not writing the converter :-)))
> Who does which page? This is a simple matter of communication.
> I do not think that we need to divide this somehow. We are just
> a few people and it suffices to document as we go. I do not think
> that we will have much problems with that. A short email on the
> list telling: hey, I'j now do the ns_XZY or Ns_XZY() would do.
Ok. But we should have a complete list for C and TCL to know whats missing or
when we are finished.
I started with TCL, but the list is not perfect:
http://naviserver.sourceforge.net/wiki/index.php/Examples:Commands
> I think that tagging the CVS now with 4.99.0 is perfectly OK as it would
> identify a body in CVS which is fixed and against which we can file
> bugs.
Ok, so we tag it after the macro insertion (or whatever solution) for the
range headers?
> I would do the 5.0 after we've done all those nice new things like VFS
> support (advancing well, btw), fancier upload caps, integration of
> ns_cache,
> full support for byte-ranges, finalized docs etc. I would target this
> towards the end of the year.
ok.
Re: [naviserver-devel] Release/Docs
Am 04.07.2005 um 08:45 schrieb Bernd Eidenschink: Hi! I want to ask you for your opinion on a few things: a) Documentation AFAIK the status was to ask Andreas Kupries for (small?) modification of the doctools to be able to make smart C-Function documentation. Zoran: Can you tell if your suggestions will be (or are) accepted? This seems to lag behind (my fault) . Basically, the doctools is allright, the only "limitation" is that you can't make one man-page describing more than one C-API call. To get an idea, install Tcl and make: man Tcl_FSStat and you will see that the *entire* Tcl-VFS API is documented in one single man-page. Now, doctools can't make this. You'd need to supply a man-page per-api-call. But... Having worked with that in last couple of days. I find it *extremely* annoying. OOH, having conceptually related calls all fit on one page is appealing. OTOH, if you frequently need (man) access to a single call, then it is absolutely impractical and annoying to flip pages and pages of docs just to locate the call in question. I would really suggest we make a simple (and doctools supported) page-per-api-call approach. The doctools can already do that and it will be easier to read and (perhaps) maintain. The drawback is: number of files (will be quite large). I think I can live with that. To me it would make sense to make the documentation effort now top priority, regardless of the format. Later we can copy and paste it from whatever source to our preferred target, but we should aim for the source now. Even the fresh NaviServer commands are not documented and only available for the skilled C developer (and see current discussion on AOLserver mailinglist). Right. In the first step documentation must not be perfect and long, as long as it respects some formal template documentation style and presents things the way they work. Strategy? Two possible ways: (A) 1. Construct list of all current commands (C and TCL), mark the deprecated ones. 2. Categorize commands. 3. We distribute documentation work among each other (small bunch of commands for everyone; and we know who documents what command); and everyone on the mailing list is a volunteer per se and likes to contribute :-) This is not an option. This has to be done for the B. (below) as well! (B) - Update the '/doc' dir in CVS using current templates OR - Update the '/doc' dir in CVS using doctools OR - use Wiki for easy peer review and parse the Wiki structure later to transform the docs to whatever format (would be very simple step) Current templates are in plan nroff and thus complex to write. I would really use doctools for this purpose. doctools have a very short learning curve (very similar to POD and very Tcl-lish) so I believe everybody will be up and running after glancing on a doctools page for a few minutes. Wiki seems very nice for collaborative work but I do not know if there is a wiki->doctools converter (doctools->wiki there is). If we start hacking wiki, how would you convert this into some other format? The AS project started this and I do not see any moves there. The wiki-entered stuff is still there and nobody cares to get it into the CVS or get it translated to other off-line reading (man, html, pdf, etc) ? Bottom line: I think the best way would be to make a template for a C-API and Tcl-API call, then check-in this template for every C/Tcl API calls in CVS, then take one at a time and fill in the content. The CVS is a collaborative env, right? Who does which page? This is a simple matter of communication. I do not think that we need to divide this somehow. We are just a few people and it suffices to document as we go. I do not think that we will have much problems with that. A short email on the list telling: hey, I'j now do the ns_XZY or Ns_XZY() would do. b) Intermediate-Release, Beta-Release This was also the intention for 4.99.0. There should be a release, downloadable!, so we have a visible result of the current status and efforts. It should be clearly marked or named as intermediate or beta release, open for testing and reviewing. Along with a statement or Roadmap that says: This release will become a default stable release - the next target is VFS, caching, etc. Do we want Version 5.0.0 to be the one with VFS, caching etc. or the first stable release? I think that tagging the CVS now with 4.99.0 is perfectly OK as it would identify a body in CVS which is fixed and against which we can file bugs. I would do the 5.0 after we've done all those nice new things like VFS support (advancing well, btw), fancier upload caps, integration of ns_cache, full support for byte-ranges, finalized docs etc. I would target this towards the end of the year. Zoran
[naviserver-devel] Release/Docs
Hi! I want to ask you for your opinion on a few things: a) Documentation AFAIK the status was to ask Andreas Kupries for (small?) modification of the doctools to be able to make smart C-Function documentation. Zoran: Can you tell if your suggestions will be (or are) accepted? To me it would make sense to make the documentation effort now top priority, regardless of the format. Later we can copy and paste it from whatever source to our preferred target, but we should aim for the source now. Even the fresh NaviServer commands are not documented and only available for the skilled C developer (and see current discussion on AOLserver mailinglist). In the first step documentation must not be perfect and long, as long as it respects some formal template documentation style and presents things the way they work. Strategy? Two possible ways: (A) 1. Construct list of all current commands (C and TCL), mark the deprecated ones. 2. Categorize commands. 3. We distribute documentation work among each other (small bunch of commands for everyone; and we know who documents what command); and everyone on the mailing list is a volunteer per se and likes to contribute :-) (B) - Update the '/doc' dir in CVS using current templates OR - Update the '/doc' dir in CVS using doctools OR - use Wiki for easy peer review and parse the Wiki structure later to transform the docs to whatever format (would be very simple step) b) Intermediate-Release, Beta-Release This was also the intention for 4.99.0. There should be a release, downloadable!, so we have a visible result of the current status and efforts. It should be clearly marked or named as intermediate or beta release, open for testing and reviewing. Along with a statement or Roadmap that says: This release will become a default stable release - the next target is VFS, caching, etc. Do we want Version 5.0.0 to be the one with VFS, caching etc. or the first stable release? What do you think? Bernd.
Re: [naviserver-devel] release ?
Hi Stephen, > http://groks.org/naviserver-4.99.0.tar.gz > > If this looks good, I'll tag it and release it to the file download > section of the site. So, make sure it still builds ok and check the > NEWS file. The NEWS file is great, everything put together at a glance. I put it on the website. Your naviserver-4.99.0.tar.gz configured,maked and compiled well on my SuSE 9.2. Bernd.
Re: [naviserver-devel] release ?
On 5/4/05, Zoran Vasiljevic <[EMAIL PROTECTED]> wrote: > Hi friends, > > ... > > I could use this occasion to raise the "are we about to make a release" > question > again. As it seems, it would be fine for us to tag the CVS and make a > tarball. > What do you think? If yes, which version? 4.99? > > Zoran Hey all. I've made some build chages lately but email notifications were busted at the time so you might not have noticed. Here's a tarball I made by cvs exporting HEAD and running make dist: http://groks.org/naviserver-4.99.0.tar.gz If this looks good, I'll tag it and release it to the file download section of the site. So, make sure it still builds ok and check the NEWS file.
Re: [naviserver-devel] release ?
Hi Stephen, > I hate to say so at this late stage, but would it be possible to keep > everything on Source Forge? :-) I would suggest to let Source Forge do the stuff you mentioned, the hard work of managing mirrored downloads, cvs, bug tracking etc. >The goal is to turn newbies into dedicated followers. >Therefore, the front page is for impressing newbies. Right. But an impressing frontpage is no matter of the underlying technology. It should be something different, more flexible, more impressing than what exists so far for the servers direct competitor ;-) The website is soon to be finished, let's see how to improve it at that time. (Btw: if it will turn out to be unstable, unnecessary etc. then switch back to SF, of course!). Regards, Bernd.
Re: [naviserver-devel] release ?
On 5/5/05, Bernd Eidenschink <[EMAIL PROTECTED]> wrote: > > Am 04.05.2005 um 16:45 schrieb Vlad Seryakov: > > > We just do not have Web site, at least first page with some details > > > would be nice. I guess, hosting on sourceforge gives us html version > > > of web page only. > > > > Bernd can take this on his shoulders, I think. Bernd? > > Yes. I will set up naviserver the next days on a server already intended for > the website. We could use www.servercult.com/naviserver or smth. like that as > we have this domain already. But this is not so important as we can change it > to whatever whenever we want. > > I'll keep you up to date. What texts do you think we need for the start (the > first promotion)? > > - Vision/Mission > - Background Info > - Where to download/How to checkout > - development guideline(s) > - ... > > Bernd. Hi! I hate to say so at this late stage, but would it be possible to keep everything on Source Forge? The nice thing about SF is that it's all managed for us. If a hard drive dies, we won't even notice. Any one of us can get busy/knocked over by a bus, without affecting any one else. We all allready have logins, and it's easy to add more, etc... Vlad raises a good point: is SF limeted to static files only? We get PHP out of the box, a MySQL database, and a few hundred megs of storage. I believe they're open to adding more stuff if we need it. Regarding the content, at this early stage we don't have a lot. In my ideal world we'd have a very focused front page with a message of why naviserver is interesting. Then we'd have a simple template we could pour the other content into as we generate it. I'm thinking about something like these: http://www.newsfirerss.com/ http://www.gnome.org/projects/f-spot/ It's blog-template-like in style with a big splashy graphic, but it's extremely direct: here's the product (often a screen shot), here's a big ol' download button, here's a tag line and a description, we're at version X. Things like forum postings and press releases are not bubbled up to the front page. The idea is there are two groups of people you're interested in: those who don't know who you are, and dedicated followers. Your dedicated followers will be subscribed to the mailing list and watch the bug tracker. The goal is to turn newbies into dedicated followers. Therefore, the front page is for impressing newbies. Besides, designing the above is much more fun than designing a portal-like page ;-) Just MHO...
Re: [naviserver-devel] release ?
Hi. There's a couple of things I've been working on which I though would be good additions for a first release, but I ran into a few problems and I haven't time to get them working. So if y'all are happy to cut a tarball now, that's fine with me. Re the numbering, I thought 4.99.0 suggested we're making pre-releases towards 5.0.0. How about we use even/odd unstable/stable releases? i.e. when 5.0 is done we move to 5.1 immediately, make a number of 5.1.x releases, and when it's stable release 5.2.0. We need to tag and branch. We'd tag odd releases, branch even ones. Odd releases are test releases, no promises. Even releases are stable releases, we may decide to backport bug fixes etc. We tag naviserver_4_99_0, we branch naviserver_5_0_0, we tag naviserver_5_0_1, we tag naviserver_5_1_13, we branch naviserver_5_2_0 ... ~ One thing it would be nice to have is a 'make dist' target. You really want the version number embedded in the configure script for that. Then you want to derive the version info in the header from that same number, rather than rely on manual syncronization. Which is a great oppertunity to introduce a config.h header and revamp the build system, including standard install paths. But then you need to teach the server init system how to find and load modules, and that code is completely broken. Hey, I got carried away :-) I'll try and break some of that up into sensible chunks early on for 4.99.1. On 5/4/05, Zoran Vasiljevic <[EMAIL PROTECTED]> wrote: > Hi friends, > > I have updated our product to use NaviServer now. It will be > distributed as > update to about 500 installations worldwide. > I have tested it thoroughly and apart from the (already noted) > ns_urlencode > (incompatibility) it seems that other things are backward-compatible > with the > aolserver. We still do not use any new features, though. This will be > added > as we pass first field-tests. > > I could use this occasion to raise the "are we about to make a release" > question > again. As it seems, it would be fine for us to tag the CVS and make a > tarball. > What do you think? If yes, which version? 4.99? > > Zoran
Re: [naviserver-devel] release ?
Am 10.05.2005 um 14:49 schrieb Bernd Eidenschink: ok. i'll try to set it up today. No rush... keep it easy going :) Zoran
Re: [naviserver-devel] release ?
> I believe we can omit all those for the beginning except the "here is > the > download link to the last release" type of thing. It costs (much) time > to get > it all written (and maintained) and we are all pretty busy... ok. i'll try to set it up today.
Re: [naviserver-devel] release ?
Am 05.05.2005 um 16:49 schrieb Bernd Eidenschink: Yes. I will set up naviserver the next days on a server already intended for the website. We could use www.servercult.com/naviserver or smth. like that as we have this domain already. But this is not so important as we can change it to whatever whenever we want. I'll keep you up to date. What texts do you think we need for the start (the first promotion)? - Vision/Mission - Background Info - Where to download/How to checkout - development guideline(s) - ... I believe we can omit all those for the beginning except the "here is the download link to the last release" type of thing. It costs (much) time to get it all written (and maintained) and we are all pretty busy... Zoran
Re: [naviserver-devel] release ?
> Am 04.05.2005 um 16:45 schrieb Vlad Seryakov: > > We just do not have Web site, at least first page with some details > > would be nice. I guess, hosting on sourceforge gives us html version > > of web page only. > > Bernd can take this on his shoulders, I think. Bernd? Yes. I will set up naviserver the next days on a server already intended for the website. We could use www.servercult.com/naviserver or smth. like that as we have this domain already. But this is not so important as we can change it to whatever whenever we want. I'll keep you up to date. What texts do you think we need for the start (the first promotion)? - Vision/Mission - Background Info - Where to download/How to checkout - development guideline(s) - ... Bernd.
Re: [naviserver-devel] release ?
Am 04.05.2005 um 16:54 schrieb Vlad Seryakov: Any ideas what? Stephen suggested 4.99. Why not use that? Or more radically, 5.0 as we do have virtual hosting now which can justify the release bump. Okay, 4.99 and we'll switch to 5.0 when docs will be ready. Good. I'm still having open discussion with Andreas (Kupries) from Tcl project about doctools package we could use to write nice-looking docs. I think I will have to speed-up this. Zoran
Re: [naviserver-devel] release ?
Any ideas what? Stephen suggested 4.99. Why not use that? Or more radically, 5.0 as we do have virtual hosting now which can justify the release bump. Okay, 4.99 and we'll switch to 5.0 when docs will be ready. -- Vlad Seryakov 571 262-8608 office [EMAIL PROTECTED] http://www.crystalballinc.com/vlad/
Re: [naviserver-devel] release ?
Am 04.05.2005 um 16:45 schrieb Vlad Seryakov: We just do not have Web site, at least first page with some details would be nice. I guess, hosting on sourceforge gives us html version of web page only. Bernd can take this on his shoulders, I think. Bernd? Also, until we have docs we can release snapshots without tagging CVS, kind of working release, i am not comfortable with CVS tagging and branching:-))) Oh, tagging is absolutely crucial! We do not need to work on the branches (yet) but it is important for us to be able to checkout the released version and make any fixes if necessary. You could ignore the branches if you like and always commit to cvs-head but we must have versioning. Using versions 4.0.x will be in collision with AS, i think new version scheme should be used. Any ideas what? Stephen suggested 4.99. Why not use that? Or more radically, 5.0 as we do have virtual hosting now which can justify the release bump. Zoran
Re: [naviserver-devel] release ?
I agree we can make public release, we wanted to do this with docs but it may take longer, so public release with official use in commercial product could be enough reason to make first appearance. We just do not have Web site, at least first page with some details would be nice. I guess, hosting on sourceforge gives us html version of web page only. Also, until we have docs we can release snapshots without tagging CVS, kind of working release, i am not comfortable with CVS tagging and branching:-))) Using versions 4.0.x will be in collision with AS, i think new version scheme should be used. Zoran Vasiljevic wrote: Hi friends, I have updated our product to use NaviServer now. It will be distributed as update to about 500 installations worldwide. I have tested it thoroughly and apart from the (already noted) ns_urlencode (incompatibility) it seems that other things are backward-compatible with the aolserver. We still do not use any new features, though. This will be added as we pass first field-tests. I could use this occasion to raise the "are we about to make a release" question again. As it seems, it would be fine for us to tag the CVS and make a tarball. What do you think? If yes, which version? 4.99? Zoran --- This SF.Net email is sponsored by: NEC IT Guy Games. Get your fingers limbered up and give it your best shot. 4 great events, 4 opportunities to win big! Highest score wins.NEC IT Guy Games. Play to win an NEC 61 plasma display. Visit http://www.necitguy.com/?r=20 ___ naviserver-devel mailing list naviserver-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/naviserver-devel -- Vlad Seryakov 571 262-8608 office [EMAIL PROTECTED] http://www.crystalballinc.com/vlad/
[naviserver-devel] release ?
Hi friends, I have updated our product to use NaviServer now. It will be distributed as update to about 500 installations worldwide. I have tested it thoroughly and apart from the (already noted) ns_urlencode (incompatibility) it seems that other things are backward-compatible with the aolserver. We still do not use any new features, though. This will be added as we pass first field-tests. I could use this occasion to raise the "are we about to make a release" question again. As it seems, it would be fine for us to tag the CVS and make a tarball. What do you think? If yes, which version? 4.99? Zoran
