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 sdea...@gmail.com 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 v...@crystalballinc.com 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
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
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
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
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 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
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 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
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 ?
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 ?
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 ?
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 ?
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/
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/
