- Dillo-dev - lists.mailman3.com

Re: [Dillo-dev] Very close to a new release!

by TheStar

> > > Note to all/self: Dillo will *not* work with autoconf-2.13. > > > > Please test our latest CVS. It should work with the old autoconf. > > Works fine now, thanks. :) I've been using 0.7.0-pre since last night; > it works beautifully so far. Can't wait for the release! > Same here, although I'd much prefer having the plugins in some generic place such as /usr/share/dillo so that I don't have to make sure that each user has the correct plugin, etc... (Can I do that already?) I'd also _really_ like to have a "open link with..." dialog/menu/etc... ;) Great job, Once the cut & paste and downloading are finished, it will be better than the graphical links!

Feb. 3, 2003

autoconf/automake stuff in CVS

by Patrick Shanahan

* Jorge Arellano Cid <jcid(a)softhome.net> [02-02-03 17:00]: > > and wrote a simple autogen.sh script to remake them. > > Now you'll need autoconf and automake installed. Built ok on SuSE 8.1, i586(686), but lost bookmarks access. Did I miss this being mentioned earlier? -- Patrick Shanahan http://wahoo.no-ip.org Registered Linux User #207535 icq#173753138 @ http://counter.li.org

Feb. 3, 2003

Re: [Dillo-dev] Very close to a new release!

by Livio Baldini Soares

Hello there! I have tested today's CVS + DPI bookmarks and things seem very well! Jorge Arellano Cid writes: [...] > With respect to staying alive, I also think it should end after > closing dillo. Maybe sending a termination request at exit time > could work fine, but I need some time to think about it... One small suggestion is that this termination be dealt with unix signals. I don't see clearly what are the advantages of using sockets for DPI's over pipes (expect running the server and the browser in different machines, but... is that useful?). Anyway, since we're using unix domain sockets, I'll assume we are local users only, and I'll also assume that signals are ok. The advantage of using signals for termination (instead of a "proper" DPI request) is that anyone can "safely" terminate a specific server. If Dillo crashes, or if it is buggy the server may dangle alive. But if you (Dillo or a user) kill with -TERM, we can have the servers set up the termination code inside the -TERM signal handler, and hence free it's resources correctly (unsaved files, opened ftp connections, etc.). If, on the other hand, there is an interest in making server and browser work on separate machines, then I would suggest to besides normal DPI termination methods, the signal termination handler still be used, as to always let the user clean things up when needed. just my 0.02 reais (which won't buy anything these days :-((( -- Livio <livio(a)ime.usp.br>

Feb. 3, 2003

Re: [Dillo-dev] Very close to a new release!

by Telent

> Note: the new bookmarks server tarball has a short program and > instructions to test permissions on *BSD machines. Someone please > give it a try. Tested on OpenBSD 3.2-current; permission denied. There's no issue there. I don't have NetBSD or FreeBSD boxes, but Open is fine. -Sunny Raspet

Feb. 3, 2003

Re: [Dillo-dev] Very close to a new release!

by Telent

> > Note to all/self: Dillo will *not* work with autoconf-2.13. > > Please test our latest CVS. It should work with the old autoconf. Works fine now, thanks. :) I've been using 0.7.0-pre since last night; it works beautifully so far. Can't wait for the release! -Sunny Raspet

Feb. 3, 2003

Re: [Dillo-dev] Very close to a new release!

by Jorge Arellano Cid

Hi there, > > The point is: testing it. Sadly I didn't received more than a > > single comment of its working. Now I'm asking again: please > > download the latest CVS, the bookmarks server, intall them, play > > with them, test and report how it works for you. > > Update'd, and it seems to work. bm_serv started automatically and > "View bookmarks", "Bookmark this page" menu commands worked. Removing > bookmarks also worked. Only problem noticed so far, is that the bm_serv > stays alive after closeing dillo (imho it shouldn't). Thanks for the feedback! (now with autoconf/automake stuff renewed in CVS, and the new bookmarks server tarball I hope it get easier to test and send some feedback!) With respect to staying alive, I also think it should end after closing dillo. Maybe sending a termination request at exit time could work fine, but I need some time to think about it... In the meanwhile, I changed the "sun" variable and also initialized "addrsize" as Melvin pointed out. AFAIU this doesn't affect those using GNU/Linux. Now you can download the latest bookmarks server and test all the stuff. Note: the new bookmarks server tarball has a short program and instructions to test permissions on *BSD machines. Someone please give it a try. Regards Jorge.- > Nice work done :) Thanks!

Feb. 2, 2003

Re: [Dillo-dev] autoconf/automake stuff in CVS

by Jorge Arellano Cid

Hi all! Considering all the troubles we've had with autoconf/automake stuff, I eliminated all these files from the CVS: Makefile.in doc/Makefile.in src/Makefile.in src/IO/Makefile.in aclocal.m4 install-sh mkinstalldirs missing depcomp (as Jörgen and others more or less suggested) and wrote a simple autogen.sh script to remake them. Now you'll need autoconf and automake installed. Ah, as the new configure.in was only working with newer versions of autoconf, I downgraded it to the same format as 0.6.6 had. I tested as far as I could here, and it should work again with older autoconf/automake pairs. Please test it and tell me. BTW, next I'll updtate the bookmars server tarball. Cheers Jorge.-

Feb. 2, 2003

Re: [Dillo-dev] autoconf/automake stuff in CVS

by Nicola Girardi

> > Makefile.in doc/Makefile.in src/Makefile.in src/IO/Makefile.in > > config.h.in configure > > aclocal.m4 (generated by aclocal) > install-sh mkinstalldirs missing depcomp (generated by automake -a) This list seems OK to me. Thanks Jorge.

Feb. 2, 2003

Re: [Dillo-dev] autoconf/automake stuff in CVS

by Jorgen Viksell

> Hi there! Hi, > Sometime ago someone suggested removing some configuration > files from the CVS. Considering all the trouble those files > generate (to allow compiling by just: ./configure; make), it > looks as a good idea. > > I'd remove: > > Makefile.in doc/Makefile.in src/Makefile.in src/IO/Makefile.in > config.h.in configure aclocal.m4 (generated by aclocal) install-sh mkinstalldirs missing depcomp (generated by automake -a) > From then, after checkout, you should run: > > autoheader; autoconf; automake; ./configure; make > > some more steps, but a lot less trouble! I think the standard way is to have an autogen.sh file that does it for you. for example: http://cvs.gnome.org/lxr/source/gob/autogen.sh So, after a checkout from cvs, you'd run ./autogen.sh --prefix=/usr ... After that it's ./configure as usual. HTH, Jörgen

Feb. 2, 2003

Re: [Dillo-dev] Very close to a new release!

by Telent

> telent@frodo:/telent/dillo% rm configure > telent@frodo:/telent/dillo% autoconf > autoconf: Undefined macros: > configure.in:153:AC_CONFIG_FILES([Makefile doc/Makefile src/Makefile > src/IO/Makefile]) > configure.in:4:AC_CONFIG_SRCDIR([src/dillo.c]) > telent@frodo:/telent/dillo% gmake > cd . && \ > /bin/sh /telent/dillo/missing --run automake --gnu Makefile > /bin/sh ./config.status --recheck > running /bin/sh ./configure --no-create --no-recursion > loading cache ./config.cache > ./configure[549]: syntax error: `src/dillo.c' unexpected > gmake: *** [config.status] Error 1 > telent@frodo:/telent/dillo% And... In the grand tradition of replying to one's own post... Yes, all my fault. Note to all/self: Dillo will *not* work with autoconf-2.13. -Sunny Raspet

Feb. 2, 2003