Menu
▾
▴
htdig-dev — Developer Discussion for the ht://Dig project
You can subscribe to this list here.
| 2001 |
Jan
|
Feb
|
Mar
|
Apr
|
May
|
Jun
|
Jul
|
Aug
|
Sep
|
Oct
(47) |
Nov
(74) |
Dec
(66) |
|---|---|---|---|---|---|---|---|---|---|---|---|---|
| 2002 |
Jan
(95) |
Feb
(102) |
Mar
(83) |
Apr
(64) |
May
(55) |
Jun
(39) |
Jul
(23) |
Aug
(77) |
Sep
(88) |
Oct
(84) |
Nov
(66) |
Dec
(46) |
| 2003 |
Jan
(56) |
Feb
(129) |
Mar
(37) |
Apr
(63) |
May
(59) |
Jun
(104) |
Jul
(48) |
Aug
(37) |
Sep
(49) |
Oct
(157) |
Nov
(119) |
Dec
(54) |
| 2004 |
Jan
(51) |
Feb
(66) |
Mar
(39) |
Apr
(113) |
May
(34) |
Jun
(136) |
Jul
(67) |
Aug
(20) |
Sep
(7) |
Oct
(10) |
Nov
(14) |
Dec
(3) |
| 2005 |
Jan
(40) |
Feb
(21) |
Mar
(26) |
Apr
(13) |
May
(6) |
Jun
(4) |
Jul
(23) |
Aug
(3) |
Sep
(1) |
Oct
(13) |
Nov
(1) |
Dec
(6) |
| 2006 |
Jan
(2) |
Feb
(4) |
Mar
(4) |
Apr
(1) |
May
(11) |
Jun
(1) |
Jul
(4) |
Aug
(4) |
Sep
|
Oct
(4) |
Nov
|
Dec
(1) |
| 2007 |
Jan
(2) |
Feb
(8) |
Mar
(1) |
Apr
(1) |
May
(1) |
Jun
|
Jul
(2) |
Aug
|
Sep
(1) |
Oct
|
Nov
|
Dec
|
| 2008 |
Jan
(1) |
Feb
|
Mar
(1) |
Apr
(2) |
May
|
Jun
|
Jul
(1) |
Aug
|
Sep
(1) |
Oct
|
Nov
|
Dec
|
| 2009 |
Jan
|
Feb
|
Mar
(2) |
Apr
|
May
(1) |
Jun
|
Jul
|
Aug
|
Sep
|
Oct
|
Nov
|
Dec
|
| 2010 |
Jan
|
Feb
|
Mar
|
Apr
|
May
|
Jun
|
Jul
|
Aug
|
Sep
|
Oct
|
Nov
|
Dec
(1) |
| 2011 |
Jan
|
Feb
|
Mar
(1) |
Apr
|
May
(1) |
Jun
|
Jul
|
Aug
|
Sep
|
Oct
(1) |
Nov
|
Dec
|
| 2012 |
Jan
|
Feb
|
Mar
|
Apr
|
May
|
Jun
|
Jul
(1) |
Aug
|
Sep
|
Oct
|
Nov
|
Dec
|
| 2013 |
Jan
|
Feb
|
Mar
|
Apr
(1) |
May
|
Jun
|
Jul
|
Aug
|
Sep
|
Oct
|
Nov
|
Dec
|
| 2016 |
Jan
(1) |
Feb
|
Mar
|
Apr
|
May
|
Jun
|
Jul
|
Aug
|
Sep
|
Oct
|
Nov
|
Dec
|
| 2017 |
Jan
|
Feb
|
Mar
|
Apr
|
May
|
Jun
|
Jul
|
Aug
|
Sep
|
Oct
|
Nov
(1) |
Dec
|
|
From: Lachlan A. <lh...@us...> - 2004-06-14 09:58:02
|
Greetings all, If htdig is interrupted, it creates the file specified in url_log (db.log by default) to contain the URLs seen but not yet visited. If this file exists, its urls are added to the next pass of the digging (if -i isn't used). My question: Is there a way to ensure that these URLs and their descendents are visited first? If so, that could be pushed as a work-around for the slow digging. Every day, a script can start an incremental dig, and kill it after X hours. If this is guaranteed to continue where it left off, it could mean that the daily digs could still be run during non-peak times. If the URLs are reordered too much, this might result in some pages never getting processed. This would probably require the file to list two classes of URLs: those processed so far, and those seen but not processed. For large data sets, that might slow the exit time down considerably. Thoughts? Lachlan -- lh...@us... ht://Dig developer DownUnder (http://www.htdig.org) |
|
From: Geoff H. <ghu...@us...> - 2004-06-13 07:16:27
|
STATUS of ht://Dig branch 3-2-x RELEASES: 3.2.0b6: Scheduled: 31 May 2004. 3.2.0b5: Released: 10 Nov 2003. 3.2.0b4: Cancelled. 3.2.0b3: Released: 22 Feb 2001. 3.2.0b2: Released: 11 Apr 2000. 3.2.0b1: Released: 4 Feb 2000. (Please note that everything added here should have a tracker PR# so we can be sure they're fixed. Geoff is currently trying to add PR#s for what's currently here.) SHOWSTOPPERS: KNOWN BUGS: (none serious. See <http://sourceforge.net/tracker/?atid=104593&group_id=4593&func=browse>.) PENDING PATCHES (available but need work): * Gilles's configuration parsing patches need testing before committing. * Memory improvements to htmerge. (Backed out b/c htword API changed.) * Mifluz merge. (Is this still pending??) NEEDED FEATURES: * Quim's new htsearch/qtest query parser framework. * File/Database locking. PR#405764. TESTING: * httools programs: (htload a test file, check a few characteristics, htdump and compare) * Tests for new config file parser * Duplicate document detection while indexing * Major revisions to ExternalParser.cc, including fork/exec instead of popen, argument handling for parser/converter, allowing binary output from an external converter. * ExternalTransport needs testing of changes similar to ExternalParser. DOCUMENTATION: * List of supported platforms/compilers is ancient. (PR#405279) * Document all of htsearch's mappings of input parameters to config attributes to template variables. (Relates to PR#405278.) Should we make sure these config attributes are all documented in defaults.cc, even if they're only set by input parameters and never in the config file? * Split attrs.html into categories for faster loading. * Turn defaults.cc into an XML file for generating documentation and defaults.cc. * require.html is not updated to list new features and disk space requirements of 3.2.x (e.g. regex matching, database compression.) PRs# 405280 #405281. * Htfuzzy could use more documentation on what each fuzzy algorithm does. PR#405714. * Document the list of all installed files and default locations. PR#405715. OTHER ISSUES: * Can htsearch actually search while an index is being created? * The code needs a security audit, esp. htsearch. PR#405765. |
|
From: Robert R. <ri...@li...> - 2004-06-12 21:37:27
|
>Message: 1 >To: htd...@li... >From: Moh...@co... >Date: Fri, 11 Jun 2004 11:13:34 -0500 >Subject: [htdig-dev] ISS box > > > > > >HI, >Does Htdig works on an IIS box with windows environment? >Please advice me on this matter. >Thank you in advance. >Mohamed. > > Hello Mohamed, htdig uses the http protocol to access files. Fot this reason it will work on any server that can serve http requests, also Microsoft Internet Information Server. If I am informed correctly there's a port of htdig to the Win32 platform, please see the website yours Robert Ribnitz ht://Dig debian maintainer |
|
From: Gabriele B. <an...@ti...> - 2004-06-12 15:58:27
|
Greetings Lachlan, At 14.08 12/06/2004, Lachlan Andrew wrote: >Yes, it is my fault for modifying only automatically generated files. >A proper patch (which I wrote before your email arrived...) is >attached. OK. Thank you. >That certainly is an option. However, doesn't it defeat the point of >that whole file? Files that were in the os directory (and being >with an os_ prefix now) were supposed to be different for each OS, to >encapsulate these differences. That said, Gabriele's solution is >probably the neater option, since all the other OS-dependent files >are just the Un*x ones. You are right Lachlan. I did not consider the aim of the file. However, if it is not a problem, I would not mind the compilation solution. I have to say though that your configure.in patch is valid as well. Please choose the one you think it is more appropriate and commit it. >You did a good job on it, Gabriele. I can't think of any real >revisions that are needed. Thank you! :-) Ciao, -Gabriele -- Gabriele Bartolini: Web Programmer, ht://Dig & IWA/HWG Member, ht://Check maintainer Current Location: Prato, Toscana, Italia an...@ti... | http://www.prato.linux.it/~gbartolini | ICQ#129221447 > "Leave every hope, ye who enter!", Dante Alighieri, Divine Comedy, The Inferno |
|
From: Gabriele B. <an...@ti...> - 2004-06-12 15:18:33
|
At 19.34 11/06/2004, Gilles Detillieux wrote:
>OK, I committed Lachlan's patch, which Joe provided in the patch archives,
>so the parser fix is in now.
Thank you Gilles.
>I did discover a little problem, though, while looking through for things
>that may have slipped through the cracks. The fixes that Lachlan had
>made back in April to get database creation working on Cygwin included
>a couple manual fixes to db/aclocal.m4 and db/configure, to switch in
>the new os_abs.c.win32 file when needed. Well, those two fixes were
>lost when Gabriele rebuilt these two scripts using autoreconf earlier
>this month. Now if I understand correctly, the configure script is
>built from configure.in and aclocal.m4, but what builds aclocal.m4 and
>how can we force that to preserve Lachlan's addition?
I am sorry about that. But if we want to easily maintain the configure
system, we should avoid manually hacking aclocal.m4 files. Usually we
should modify the acinclude.m4 and regenerate aclocal.m4 through aclocal.
In this case however, I would suggest a different approach, that is to say
insert a conditional compilation into the os_abs.c file. At the end there
is the simple patch I'd commit. Let me know what you think and if you have
the chance to try it, let me know (I don't have any C++ compiler on Windows).
>I suppose we can manually re-add this fix to these two files before
>releasing b6, and deal with the problem properly later, but we really
>need to deal with this. The problem with all these autotools is that
>it's extremely difficult to keep straight what builds what (and what
>clobbers what!), so how to you make changes permanent?
I would stick with this solution, which I consider more linear (after all I
think it is a source problem, not an environment detection one).
>Gabriele and Lachlan, I'll throw this in your hands. You can decide
>between the two of you how you want this fixed for b6 and for 3.2.0 final,
>and how much this should (further) delay the b6 release.
We say: we've done 100, let's do 101 ... I would rather wait until this is
fixed too and release 3.2.0b6. I think we've done a superb job especially
in the last week, thanks to the contribution of all of you guys.
I ask you another big favour: if someone of you could please revise the
Release.html file.
Ciao and thanks,
-Gabriele
--- os_abs.c 2 Feb 2002 18:18:05 -0000 1.2
+++ os_abs.c 12 Jun 2004 07:43:03 -0000
@@ -27,5 +27,9 @@ int
CDB___os_abspath(path)
const char *path;
{
+#if defined (_WIN32) || defined (__MSDOS__) || defined (__DJGPP__) ||
defined (__CYGWIN__)
+ return (path[0] == '/' || path[0] == '\\' || path [1] == ':');
+#else
return (path[0] == '/');
+#endif
}
|
|
From: Lachlan A. <lh...@us...> - 2004-06-12 13:12:34
|
Greetings all,
The htmerge.html documentation currently says
Note: You must run htmerge separately on each of the databases
created by htdig before merging them together with this option.
This is because merging the two wordlists together requires
wordlists that have already been cleaned up by htmerge.
Am I correct in thinking that this is a carry-over from 3.1.x, and is
no longer true?
Thanks,
Lachlan
--
lh...@us...
ht://Dig developer DownUnder (http://www.htdig.org)
|
|
From: Lachlan A. <lh...@us...> - 2004-06-12 12:09:21
|
Greetings all, On Sat, 12 Jun 2004 05:50 pm, Gabriele Bartolini wrote: > I am sorry about that. But if we want to easily maintain the > configure system, we should avoid manually hacking aclocal.m4 > files. Usually we should modify the acinclude.m4 and regenerate > aclocal.m4 through aclocal. Yes, it is my fault for modifying only automatically generated files. A proper patch (which I wrote before your email arrived...) is attached. > In this case however, I would suggest a different approach, that is > to say insert a conditional compilation into the os_abs.c file. At > the end there is the simple patch I'd commit. Let me know what you > think and if you have the chance to try it, let me know (I don't > have any C++ compiler on Windows). > That certainly is an option. However, doesn't it defeat the point of that whole file? Files that were in the os directory (and being with an os_ prefix now) were supposed to be different for each OS, to encapsulate these differences. That said, Gabriele's solution is probably the neater option, since all the other OS-dependent files are just the Un*x ones. > I ask you another big favour: if someone of you could please revise > the Release.html file. You did a good job on it, Gabriele. I can't think of any real revisions that are needed. Cheers, Lachlan -- lh...@us... ht://Dig developer DownUnder (http://www.htdig.org) |
|
From: Lachlan A. <lh...@us...> - 2004-06-12 07:31:07
|
Greetings Mohamed, Forgive my ignorance, by I don't know what IIS is. However, ht://Dig does run on windows. Most versions work under Cygwin, which provides a unix-like environment. Neal Richter also recently ported it to run "natively" under window, but the documentation on how to install that has not yet been written. I hope this helps, Lachlan On Sat, 12 Jun 2004 02:13 am, Moh...@co... wrote: > Does Htdig works on an IIS box with windows environment? > Please advice me on this matter. -- lh...@us... ht://Dig developer DownUnder (http://www.htdig.org) |
|
From: Gilles D. <gr...@sc...> - 2004-06-11 17:34:25
|
According to an...@ti...: > Is it possible to have this patch so that I can commit it before 3.2.0b6 > is released? Thank you very much. OK, I committed Lachlan's patch, which Joe provided in the patch archives, so the parser fix is in now. I also made about four other changes which were things that had slipped through the cracks, and I rediscovered this morning while looking at RPMs of htdig. I through in one of Red Hat's patches to db/hash.c, which I can't imagine breaking anything. I did discover a little problem, though, while looking through for things that may have slipped through the cracks. The fixes that Lachlan had made back in April to get database creation working on Cygwin included a couple manual fixes to db/aclocal.m4 and db/configure, to switch in the new os_abs.c.win32 file when needed. Well, those two fixes were lost when Gabriele rebuilt these two scripts using autoreconf earlier this month. Now if I understand correctly, the configure script is built from configure.in and aclocal.m4, but what builds aclocal.m4 and how can we force that to preserve Lachlan's addition? I suppose we can manually re-add this fix to these two files before releasing b6, and deal with the problem properly later, but we really need to deal with this. The problem with all these autotools is that it's extremely difficult to keep straight what builds what (and what clobbers what!), so how to you make changes permanent? Gabriele and Lachlan, I'll throw this in your hands. You can decide between the two of you how you want this fixed for b6 and for 3.2.0 final, and how much this should (further) delay the b6 release. -- Gilles R. Detillieux E-mail: <gr...@sc...> Spinal Cord Research Centre WWW: http://www.scrc.umanitoba.ca/ Dept. Physiology, U. of Manitoba Winnipeg, MB R3E 3J7 (Canada) |
|
From: Joe R. J. <jj...@cl...> - 2004-06-11 16:15:14
|
On Fri, 11 Jun 2004 an...@ti... wrote:
> Date: Fri, 11 Jun 2004 09:46:12 +0200
> From: an...@ti...
> To: Joe R. Jah <jj...@cl...>, lac...@ip...
> Cc: Christopher Murtagh <chr...@mc...>,
htd...@li...
> Subject: Re: [htdig-dev] boolean terms in phrase - bug?
>
> Hi guys,
>
> Is it possible to have this patch so that I can commit it before 3.2.0b6
> is released? Thank you very much.
>
> -Gabriele
>
ftp://ftp.ccsf.org/htdig-patches/3.2.0b5/boolean-patch.0
I have tested it successfully; it is now in production;) Chris also
reported to have successfully tested it.
Regards,
Joe
--
_/ _/_/_/ _/ ____________ __o
_/ _/ _/ _/ ______________ _-\<,_
_/ _/ _/_/_/ _/ _/ ......(_)/ (_)
_/_/ oe _/ _/. _/_/ ah jj...@cl...
> >-- Messaggio originale --
> >From: "Joe R. Jah" <jj...@cl...>
> >To: lac...@ip...
> >cc: Christopher Murtagh <chr...@mc...>,
> > htd...@li...
> >Subject: Re: [htdig-dev] boolean terms in phrase - bug?
> >Date: Thu, 10 Jun 2004 23:35:36 -0700 (PDT)
> >
> >
> >On Fri, 11 Jun 2004 lac...@ip... wrote:
> >
> >> Date: Fri, 11 Jun 2004 11:46:59 +1000
> >> From: lac...@ip...
> >> To: Joe R. Jah <jj...@cl...>,
> > Christopher Murtagh <chr...@mc...>
> >> Cc: htd...@li...
> >> Subject: Re: [htdig-dev] boolean terms in phrase - bug?
> >>
> >> Greetings all,
> >>
> >> The attached patch should get things working.
> >
> >Thanks Lachlan. What a relief! I have enabled boolean option on my
> >search forms again;)
> >
> >Regards,
> >
> >Joe
> >--
> > _/ _/_/_/ _/ ____________ __o
> > _/ _/ _/ _/ ______________ _-\<,_
> > _/ _/ _/_/_/ _/ _/ ......(_)/ (_)
> > _/_/ oe _/ _/. _/_/ ah jj...@cl...
> >
> >> Thanks again, Chris, for pointing this bug out.
> >>
> >> Cheers,
> >> Lachlan
> >>
> >>
> >> >-- Original Message --
> >> >On Wed, 9 Jun 2004, Christopher Murtagh wrote:
> >> >
> >> >> That's what I thought. Thanks for the feedback. In my position, I'm
> >> >> fortunate that I have a php wrapper that is cleaning up all input
> before
> >> >> it is sent to htsearch, so I can write a little function that will
> strip
> >> >> these. However, it might be a good idea for the htdig team to let
> other
> >> >> folks who are currently using 3.2 in production about this as this
> makes
> >> >> it easy to cripple any machine running htdig 3.2 with boolean search
> >> >> feature.
|
|
From: <Moh...@co...> - 2004-06-11 16:13:46
|
HI, Does Htdig works on an IIS box with windows environment? Please advice me on this matter. Thank you in advance. Mohamed. |
|
From: Christopher M. <chr...@mc...> - 2004-06-11 15:07:06
|
On Thu, 2004-06-10 at 21:46, lac...@ip... wrote: > The attached patch should get things working. Awesome. I've tested the patch on my machine and it works perfectly. > Thanks again, Chris, for pointing this bug out. Thanks to you for such a fast fix, and to the htdig team for this great software! Cheers, Chris -- Christopher Murtagh Enterprise Systems Administrator ISR / Web Communications Group McGill University Montreal, Quebec Canada Tel.: (514) 398-3122 Fax: (514) 398-2017 |
|
From: <an...@ti...> - 2004-06-11 07:46:39
|
Hi guys, Is it possible to have this patch so that I can commit it before 3.2.0= b6 is released? Thank you very much. -Gabriele >-- Messaggio originale -- >From: "Joe R. Jah" <jj...@cl...> >To: lac...@ip... >cc: Christopher Murtagh <chr...@mc...>, > htd...@li... >Subject: Re: [htdig-dev] boolean terms in phrase - bug? >Date: Thu, 10 Jun 2004 23:35:36 -0700 (PDT) > > >On Fri, 11 Jun 2004 lac...@ip... wrote: > >> Date: Fri, 11 Jun 2004 11:46:59 +1000 >> From: lac...@ip... >> To: Joe R. Jah <jj...@cl...>, > Christopher Murtagh <chr...@mc...> >> Cc: htd...@li... >> Subject: Re: [htdig-dev] boolean terms in phrase - bug? >> >> Greetings all, >> >> The attached patch should get things working. > >Thanks Lachlan. What a relief! I have enabled boolean option on my >search forms again;) > >Regards, > >Joe >-- > _/ _/_/_/ _/ ____________ __o > _/ _/ _/ _/ ______________ _-\<,_ > _/ _/ _/_/_/ _/ _/ ......(_)/ (_) > _/_/ oe _/ _/. _/_/ ah jj...@cl... > >> Thanks again, Chris, for pointing this bug out. >> >> Cheers, >> Lachlan >> >> >> >-- Original Message -- >> >On Wed, 9 Jun 2004, Christopher Murtagh wrote: >> > >> >> That's what I thought. Thanks for the feedback. In my position, I'= m >> >> fortunate that I have a php wrapper that is cleaning up all input before >> >> it is sent to htsearch, so I can write a little function that will strip >> >> these. However, it might be a good idea for the htdig team to let other >> >> folks who are currently using 3.2 in production about this as this makes >> >> it easy to cripple any machine running htdig 3.2 with boolean searc= h >> >> feature. > > > >------------------------------------------------------- >This SF.Net email is sponsored by the new InstallShield X. >From Windows to Linux, servers to mobile, InstallShield X is the >one installation-authoring solution that does it all. Learn more and >evaluate today! http://www.installshield.com/Dev2Dev/0504 >_______________________________________________ >ht://Dig Developer mailing list: >htd...@li... >List information (subscribe/unsubscribe, etc.) >https://lists.sourceforge.net/lists/listinfo/htdig-dev |
|
From: Joe R. J. <jj...@cl...> - 2004-06-11 06:35:45
|
On Fri, 11 Jun 2004 lac...@ip... wrote:
> Date: Fri, 11 Jun 2004 11:46:59 +1000
> From: lac...@ip...
> To: Joe R. Jah <jj...@cl...>,
Christopher Murtagh <chr...@mc...>
> Cc: htd...@li...
> Subject: Re: [htdig-dev] boolean terms in phrase - bug?
>
> Greetings all,
>
> The attached patch should get things working.
Thanks Lachlan. What a relief! I have enabled boolean option on my
search forms again;)
Regards,
Joe
--
_/ _/_/_/ _/ ____________ __o
_/ _/ _/ _/ ______________ _-\<,_
_/ _/ _/_/_/ _/ _/ ......(_)/ (_)
_/_/ oe _/ _/. _/_/ ah jj...@cl...
> Thanks again, Chris, for pointing this bug out.
>
> Cheers,
> Lachlan
>
>
> >-- Original Message --
> >On Wed, 9 Jun 2004, Christopher Murtagh wrote:
> >
> >> That's what I thought. Thanks for the feedback. In my position, I'm
> >> fortunate that I have a php wrapper that is cleaning up all input before
> >> it is sent to htsearch, so I can write a little function that will strip
> >> these. However, it might be a good idea for the htdig team to let other
> >> folks who are currently using 3.2 in production about this as this makes
> >> it easy to cripple any machine running htdig 3.2 with boolean search
> >> feature.
|
|
From: <lac...@ip...> - 2004-06-11 01:47:19
|
Greetings all, The attached patch should get things working. Thanks again, Chris, for pointing this bug out. Cheers, Lachlan >-- Original Message -- >On Wed, 9 Jun 2004, Christopher Murtagh wrote: > >> That's what I thought. Thanks for the feedback. In my position, I'm >> fortunate that I have a php wrapper that is cleaning up all input before >> it is sent to htsearch, so I can write a little function that will strip >> these. However, it might be a good idea for the htdig team to let other >> folks who are currently using 3.2 in production about this as this makes >> it easy to cripple any machine running htdig 3.2 with boolean search >> feature. |
|
From: <lac...@ip...> - 2004-06-11 00:37:25
|
Greetings Dominique, When you've done that, you might offer the new version to the site you got the old one from. Open source software works because of everyone's contributions :) Thanks, Lachlan >-- Original Message -- >Subject: Re: [htdig-dev] Re: Accents, endings and chaining >From: "Dominique Arpin" <dom...@es...> > >Thanks for the help, its work perfectly. I just need to complete french.0 >file for new words. |
|
From: <lac...@ip...> - 2004-06-11 00:32:39
|
Thanks Joe. I'll apply patch 3 to CVS when I next get to my PC. The problem with t_htdig has already been fixed. (I'm really not sure why it worked under gnu/linux -- the script definitely had a bug.) Cheers, Lachlan >-- Original Message -- >Date: Wed, 9 Jun 2004 23:49:23 -0700 (PDT) >From: "Joe R. Jah" <jj...@cl...> >To: Lachlan Andrew <lh...@us...> >cc: htd...@li... >Subject: Re: [htdig-dev] Make check and htdig warnings > > >On Wed, 9 Jun 2004, Lachlan Andrew wrote: > >> Date: Wed, 9 Jun 2004 20:49:47 +1000 >> From: Lachlan Andrew <lh...@us...> >> To: Joe R. Jah <jj...@cl...>, htd...@li... >> Subject: Re: [htdig-dev] Make check and htdig warnings >> >> On Wed, 9 Jun 2004 03:41 pm, Joe R. Jah wrote: >> > Hi Folks, >> > >> > Make check errors on BSD/OS 4.3.1: >> > >> > ../htlib/.libs/libht.a(HtWordType.o): In function >> > `HtStripPunctuation(String &)': >> > /tmp/htdig-3.2.0b6/htlib/../htword/WordType.h:66: undefined >> > reference to `WordType::instance' gmake[2]: *** [testnet] Error 1 >> >> Greetings Joe, >> >> This is the same problem as Jesse was getting on HP-UX... To hunt >> this problem down, could you please >> 1. Try the explicit g++ command I suggested in >> <http://www.mail-archive.com/htd...@li.../msg02078.html> > > cd test > g++ -g -O2 -Wall -fno-rtti -fno-exceptions -o testnet testnet.o \ > -L/opt/htdig/lib/zlib/lib ../htnet/.libs/libhtnet.a \ > ../htcommon/.libs/libcommon.a ../htword/.libs/libhtword.a \ > ../db/.libs/libhtdb.a ../htlib/.libs/libht.a \ > ../htword/.libs/libhtword.a -lz > gmake check > >../htlib/.libs/libht.a(HtWordType.o): In function `HtIsWordChar(char)': >/usr/src/WWW/htdig/htdig-3.2.0b6/htlib/../htword/WordType.h:66: undefined >reference to `WordType::instance' >../htlib/.libs/libht.a(HtWordType.o): In function `HtIsStrictWordChar(char)': >/usr/src/WWW/htdig/htdig-3.2.0b6/htlib/../htword/WordType.h:66: undefined >reference to `WordType::instance' >../htlib/.libs/libht.a(HtWordType.o): In function `HtWordNormalize(String >&)': >/usr/src/WWW/htdig/htdig-3.2.0b6/htlib/../htword/WordType.h:66: undefined >reference to `WordType::instance' >../htlib/.libs/libht.a(HtWordType.o): In function `HtStripPunctuation(String >&)': >/usr/src/WWW/htdig/htdig-3.2.0b6/htlib/../htword/WordType.h:66: undefined >reference to `WordType::instance' >gmake[1]: *** [url] Error 1 >gmake[1]: Leaving directory `/usr/src/WWW/htdig/htdig-3.2.0b6/test' >gmake: *** [check-am] Error 2 > >> 2. Replace '--mode=link' by '--mode=link --preserve-dup-deps' in >> line 324 of test/Makefile and then try make check again. > >../htlib/.libs/libht.a(HtWordType.o): In function `HtIsWordChar(char)': >/usr/src/WWW/htdig/htdig-3.2.0b6/htlib/../htword/WordType.h:66: undefined >reference to `WordType::instance' >../htlib/.libs/libht.a(HtWordType.o): In function `HtIsStrictWordChar(char)': >/usr/src/WWW/htdig/htdig-3.2.0b6/htlib/../htword/WordType.h:66: undefined >reference to `WordType::instance' >../htlib/.libs/libht.a(HtWordType.o): In function `HtWordNormalize(String >&)': >/usr/src/WWW/htdig/htdig-3.2.0b6/htlib/../htword/WordType.h:66: undefined >reference to `WordType::instance' >../htlib/.libs/libht.a(HtWordType.o): In function `HtStripPunctuation(String >&)': >/usr/src/WWW/htdig/htdig-3.2.0b6/htlib/../htword/WordType.h:66: undefined >reference to `WordType::instance' >*** Error code 1 > >Stop. >*** Error code 1 > >Stop. > >> 3. Replace the line something like >> HTLIBS = $(top_builddir)/htnet/libhtnet.la \ >> $(top_builddir)/htcommon/libcommon.la \ >> $(top_builddir)/htword/libhtword.la \ >> $(top_builddir)/htlib/libht.la \ >> $(top_builddir)/htcommon/libcommon.la \ >> $(top_builddir)/htword/libhtword.la \ >> $(top_builddir)/db/libhtdb.la \ >> $(top_builddir)/htlib/libht.la >> in test/Makefile, by a line like >> HTLIBS = $(top_builddir)/htnet/libhtnet.la \ >> $(top_builddir)/htcommon/libcommon.la \ >> $(top_builddir)/htword/libhtword.la \ >> $(top_builddir)/htlib/libht.la \ >> $(top_builddir)/./htcommon/libcommon.la \ >> $(top_builddir)/./htword/libhtword.la \ >> $(top_builddir)/./db/libhtdb.la \ >> $(top_builddir)/./htlib/libht.la >> (that is, for the repeated libraries, add a './' to the path) and >> then rerun make check. > > >PASS: t_wordkey >PASS: t_wordlist >PASS: t_wordskip >PASS: t_wordbitstream >PASS: t_search >PASS: t_htdb >PASS: t_rdonly >PASS: t_trunc >PASS: t_url > >dodoc: cannot open >running htdig: expected >http://localhost:7400/set1/ >http://localhost:7400/set1/bad_local.htm >http://localhost:7400/set1/script.html >http://localhost:7400/set1/site%201.html >http://localhost:7400/set1/site2.html >http://localhost:7400/set1/site3.html >http://localhost:7400/set1/site4.html >http://localhost:7400/set1/sub%2520dir/ >http://localhost:7400/set1/sub%2520dir/empty%20file.html >http://localhost:7400/set1/title.html >but got > >htpurge: Database is empty! > >FAIL: t_htdig >PASS: t_htsearch >PASS: t_htmerge >PASS: t_htnet >PASS: t_htdig_local >PASS: t_factors >PASS: t_fuzzy >PASS: t_parsing >PASS: t_templates >PASS: t_validwords >==================== >1 of 19 tests failed >*** Error code 1 > >Stop. >*** Error code 1 > >Stop. > >> 4. Type >> nm htword/.libs/libhtword.a | grep instance > > U _10WordDBInfo.instance > U _11WordKeyInfo.instance > U _11WordMonitor.instance > U _14WordRecordInfo.instance > U _8WordType.instance > U _11WordKeyInfo.instance > U _14WordRecordInfo.instance > U _10WordDBInfo.instance > U _11WordKeyInfo.instance >0000039c D _10WordDBInfo.instance > U _11WordKeyInfo.instance > U _14WordRecordInfo.instance > U _11WordKeyInfo.instance >000008f8 D _11WordKeyInfo.instance > U _10WordDBInfo.instance > U _11WordKeyInfo.instance > U _14WordRecordInfo.instance >00000870 D _11WordMonitor.instance >00000160 D _14WordRecordInfo.instance > U _11WordKeyInfo.instance > U _14WordRecordInfo.instance >00000988 D _8WordType.instance > > >> nm test/testnet.o | grep instance > >> 5. Type >> cp /bin/true test/testnet > >It was actually cp /usr/bin/true test/testnet > >> make check > >PASS: t_wordkey >PASS: t_wordlist >PASS: t_wordskip >PASS: t_wordbitstream >PASS: t_search >PASS: t_htdb >PASS: t_rdonly >PASS: t_trunc >PASS: t_url >running htdig: expected >http://localhost:7400/set1/ >http://localhost:7400/set1/bad_local.htm >http://localhost:7400/set1/script.html >http://localhost:7400/set1/site%201.html >http://localhost:7400/set1/site2.html >http://localhost:7400/set1/site3.html >http://localhost:7400/set1/site4.html >http://localhost:7400/set1/sub%2520dir/ >http://localhost:7400/set1/sub%2520dir/empty%20file.html >http://localhost:7400/set1/title.html >but got > >FAIL: t_htdig >PASS: t_htsearch >PASS: t_htmerge >Could not fetch URL >FAIL: t_htnet >PASS: t_htdig_local >PASS: t_factors >PASS: t_fuzzy >PASS: t_parsing >PASS: t_templates >PASS: t_validwords >==================== >2 of 19 tests failed >==================== >gmake[1]: *** [check-TESTS] Error 1 >gmake[1]: Leaving directory `/usr/src/WWW/htdig/htdig-3.2.0b6/test' >gmake: *** [check-am] Error 2 > >> > Warnings from htdig: >> > >> > Warning: Configuration option heading_factor_1 is no longer supported >> > Warning: Configuration option heading_factor_2 is no longer supported >> > Warning: Configuration option heading_factor_3 is no longer supported >> > Warning: Configuration option heading_factor_4 is no longer supported >> > Warning: Configuration option heading_factor_5 is no longer supported >> > Warning: Configuration option heading_factor_6 is no longer supported >> > Warning: Configuration option modification_time_is_now is no longer supported >> > Warning: Configuration option pdf_parser is no longer supported >> > Warning: Configuration option translate_amp is no longer supported >> > Warning: Configuration option translate_lt_gt is no longer supported >> > Warning: Configuration option translate_quot is no longer supported >> > >> > Huh? >> >> Because people were confused by pdf_parser no longer working in >> ht://Dig, it now checks for old 3.1.x configuration attributes which >> are in the htdig.conf file but not supported by ht://Dig 3.2.x >> Are any of these options specified in your htdig.conf? If not, this >> is a bug... > >Thanks Lachlan; yes I had all those attributes from 3.1.x days left in my >htdig.conf file. > >Regards, > >Joe >-- > _/ _/_/_/ _/ ____________ __o > _/ _/ _/ _/ ______________ _-\<,_ > _/ _/ _/_/_/ _/ _/ ......(_)/ (_) > _/_/ oe _/ _/. _/_/ ah jj...@cl... > |
|
From: <lac...@ip...> - 2004-06-11 00:20:18
|
Greetings all (especially Gabriele), I think that this DoS bug is serious enough to be a showstopper for 3.2.0b6. I'll try to look at it over the weekend... Lachlan >-- Original Message -- >From: Christopher Murtagh <chr...@mc...> >Subject: Re: [htdig-dev] boolean terms in phrase - bug? >To: "Joe R. Jah" <jj...@cl...> >Cc: htd...@li... >Date: Wed, 09 Jun 2004 23:39:02 -0400 > > >On Wed, 2004-06-09 at 15:28, Joe R. Jah wrote: >> It's a serious BUG;( > > That's what I thought. Thanks for the feedback. In my position, I'm >fortunate that I have a php wrapper that is cleaning up all input before >it is sent to htsearch, so I can write a little function that will strip >these. However, it might be a good idea for the htdig team to let other >folks who are currently using 3.2 in production about this as this makes >it easy to cripple any machine running htdig 3.2 with boolean search >feature. > >Cheers, > >Chris |
|
From: Gabriele B. <g.b...@co...> - 2004-06-10 16:08:59
|
Ciao Lachlan, Il mer, 2004-06-09 alle 13:42, Lachlan Andrew ha scritto: > Sorry, I didn't get to read my email yesterday. I've just applied a > patch to support OpenOffice.org documents. I don't mind if it misses > out on 3.2.0b6, but I hope it doesn't cause you any problems. No worries. I included - if you don't mind - your changes into the release. Let me know if you don't agree. > Thanks for doing the release!! Thank you! Ciao, -Gabriele |
|
From: Gabriele B. <g.b...@co...> - 2004-06-10 15:57:18
|
Hi Gilles, Il gio, 2004-06-10 alle 16:26, Gilles Detillieux ha scritto: > Well, conf_parser.cxx should be fine in my patch from yesterday. > It's conf_lexer.cxx that I'd like you to regenerate, and then commit > all 4 htcommon/conf_*.?xx files to cvs. If you do that today, it'll > at least give the other developers almost a day to test on the various > platforms before releasing. If that's too rushed, we can hold off the > release till Monday. Thoughts? I've just committed the patch (thank you for that) and regenerated the conf_lexer.cxx file. I have rebuilt the 3.2.0b6 tarball and put it under the files section (http://www.htdig.org/files/). Please guys have a try and let me know whether to proceed or not with the release or delay it till monday. Ciao, -Gabriele |
|
From: Gilles D. <gr...@sc...> - 2004-06-10 14:26:51
|
According to Gabriele Bartolini: > >this patch to go into b6, but it would be a good idea if a few other > >developers tested it first, as I asked back in April. All I can say is > >it works for me (but I tested it using flex 2.5.4a, and only on RH 9). > > You are right. I did not have a chance to try it before. However, tomorrow > I will regenerate the conf_parser.cxx file and commit the changes, and > prepare the new release tarball. If everything is fine, I will release > 3.2.0b6 on friday morning Central Europe Time. Sounds good? Well, conf_parser.cxx should be fine in my patch from yesterday. It's conf_lexer.cxx that I'd like you to regenerate, and then commit all 4 htcommon/conf_*.?xx files to cvs. If you do that today, it'll at least give the other developers almost a day to test on the various platforms before releasing. If that's too rushed, we can hold off the release till Monday. Thoughts? -- Gilles R. Detillieux E-mail: <gr...@sc...> Spinal Cord Research Centre WWW: http://www.scrc.umanitoba.ca/ Dept. Physiology, U. of Manitoba Winnipeg, MB R3E 3J7 (Canada) |
|
From: Joe R. J. <jj...@cl...> - 2004-06-10 06:52:08
|
On Wed, 9 Jun 2004, Christopher Murtagh wrote:
> Date: Wed, 09 Jun 2004 23:39:02 -0400
> From: Christopher Murtagh <chr...@mc...>
> To: Joe R. Jah <jj...@cl...>
> Cc: htd...@li...
> Subject: Re: [htdig-dev] boolean terms in phrase - bug?
>
> On Wed, 2004-06-09 at 15:28, Joe R. Jah wrote:
> > It's a serious BUG;(
>
> That's what I thought. Thanks for the feedback. In my position, I'm
> fortunate that I have a php wrapper that is cleaning up all input before
> it is sent to htsearch, so I can write a little function that will strip
> these. However, it might be a good idea for the htdig team to let other
> folks who are currently using 3.2 in production about this as this makes
> it easy to cripple any machine running htdig 3.2 with boolean search
> feature.
If the wrapper changes the phrase, you would be searching for a different
phrase; right?
There must be a way to distinguish boolean_keywords contained in quoted
phrases, from those outside of quotes in htsearch; libhtdig_htsearch.cc?
Regards,
Joe
--
_/ _/_/_/ _/ ____________ __o
_/ _/ _/ _/ ______________ _-\<,_
_/ _/ _/_/_/ _/ _/ ......(_)/ (_)
_/_/ oe _/ _/. _/_/ ah jj...@cl...
|
|
From: Joe R. J. <jj...@cl...> - 2004-06-10 06:49:29
|
On Wed, 9 Jun 2004, Lachlan Andrew wrote: > Date: Wed, 9 Jun 2004 20:49:47 +1000 > From: Lachlan Andrew <lh...@us...> > To: Joe R. Jah <jj...@cl...>, htd...@li... > Subject: Re: [htdig-dev] Make check and htdig warnings > > On Wed, 9 Jun 2004 03:41 pm, Joe R. Jah wrote: > > Hi Folks, > > > > Make check errors on BSD/OS 4.3.1: > > > > ../htlib/.libs/libht.a(HtWordType.o): In function > > `HtStripPunctuation(String &)': > > /tmp/htdig-3.2.0b6/htlib/../htword/WordType.h:66: undefined > > reference to `WordType::instance' gmake[2]: *** [testnet] Error 1 > > Greetings Joe, > > This is the same problem as Jesse was getting on HP-UX... To hunt > this problem down, could you please > 1. Try the explicit g++ command I suggested in > <http://www.mail-archive.com/htd...@li.../msg02078.html> cd test g++ -g -O2 -Wall -fno-rtti -fno-exceptions -o testnet testnet.o \ -L/opt/htdig/lib/zlib/lib ../htnet/.libs/libhtnet.a \ ../htcommon/.libs/libcommon.a ../htword/.libs/libhtword.a \ ../db/.libs/libhtdb.a ../htlib/.libs/libht.a \ ../htword/.libs/libhtword.a -lz gmake check ../htlib/.libs/libht.a(HtWordType.o): In function `HtIsWordChar(char)': /usr/src/WWW/htdig/htdig-3.2.0b6/htlib/../htword/WordType.h:66: undefined reference to `WordType::instance' ../htlib/.libs/libht.a(HtWordType.o): In function `HtIsStrictWordChar(char)': /usr/src/WWW/htdig/htdig-3.2.0b6/htlib/../htword/WordType.h:66: undefined reference to `WordType::instance' ../htlib/.libs/libht.a(HtWordType.o): In function `HtWordNormalize(String &)': /usr/src/WWW/htdig/htdig-3.2.0b6/htlib/../htword/WordType.h:66: undefined reference to `WordType::instance' ../htlib/.libs/libht.a(HtWordType.o): In function `HtStripPunctuation(String &)': /usr/src/WWW/htdig/htdig-3.2.0b6/htlib/../htword/WordType.h:66: undefined reference to `WordType::instance' gmake[1]: *** [url] Error 1 gmake[1]: Leaving directory `/usr/src/WWW/htdig/htdig-3.2.0b6/test' gmake: *** [check-am] Error 2 > 2. Replace '--mode=link' by '--mode=link --preserve-dup-deps' in > line 324 of test/Makefile and then try make check again. ../htlib/.libs/libht.a(HtWordType.o): In function `HtIsWordChar(char)': /usr/src/WWW/htdig/htdig-3.2.0b6/htlib/../htword/WordType.h:66: undefined reference to `WordType::instance' ../htlib/.libs/libht.a(HtWordType.o): In function `HtIsStrictWordChar(char)': /usr/src/WWW/htdig/htdig-3.2.0b6/htlib/../htword/WordType.h:66: undefined reference to `WordType::instance' ../htlib/.libs/libht.a(HtWordType.o): In function `HtWordNormalize(String &)': /usr/src/WWW/htdig/htdig-3.2.0b6/htlib/../htword/WordType.h:66: undefined reference to `WordType::instance' ../htlib/.libs/libht.a(HtWordType.o): In function `HtStripPunctuation(String &)': /usr/src/WWW/htdig/htdig-3.2.0b6/htlib/../htword/WordType.h:66: undefined reference to `WordType::instance' *** Error code 1 Stop. *** Error code 1 Stop. > 3. Replace the line something like > HTLIBS = $(top_builddir)/htnet/libhtnet.la \ > $(top_builddir)/htcommon/libcommon.la \ > $(top_builddir)/htword/libhtword.la \ > $(top_builddir)/htlib/libht.la \ > $(top_builddir)/htcommon/libcommon.la \ > $(top_builddir)/htword/libhtword.la \ > $(top_builddir)/db/libhtdb.la \ > $(top_builddir)/htlib/libht.la > in test/Makefile, by a line like > HTLIBS = $(top_builddir)/htnet/libhtnet.la \ > $(top_builddir)/htcommon/libcommon.la \ > $(top_builddir)/htword/libhtword.la \ > $(top_builddir)/htlib/libht.la \ > $(top_builddir)/./htcommon/libcommon.la \ > $(top_builddir)/./htword/libhtword.la \ > $(top_builddir)/./db/libhtdb.la \ > $(top_builddir)/./htlib/libht.la > (that is, for the repeated libraries, add a './' to the path) and > then rerun make check. PASS: t_wordkey PASS: t_wordlist PASS: t_wordskip PASS: t_wordbitstream PASS: t_search PASS: t_htdb PASS: t_rdonly PASS: t_trunc PASS: t_url dodoc: cannot open running htdig: expected http://localhost:7400/set1/ http://localhost:7400/set1/bad_local.htm http://localhost:7400/set1/script.html http://localhost:7400/set1/site%201.html http://localhost:7400/set1/site2.html http://localhost:7400/set1/site3.html http://localhost:7400/set1/site4.html http://localhost:7400/set1/sub%2520dir/ http://localhost:7400/set1/sub%2520dir/empty%20file.html http://localhost:7400/set1/title.html but got htpurge: Database is empty! FAIL: t_htdig PASS: t_htsearch PASS: t_htmerge PASS: t_htnet PASS: t_htdig_local PASS: t_factors PASS: t_fuzzy PASS: t_parsing PASS: t_templates PASS: t_validwords ==================== 1 of 19 tests failed *** Error code 1 Stop. *** Error code 1 Stop. > 4. Type > nm htword/.libs/libhtword.a | grep instance U _10WordDBInfo.instance U _11WordKeyInfo.instance U _11WordMonitor.instance U _14WordRecordInfo.instance U _8WordType.instance U _11WordKeyInfo.instance U _14WordRecordInfo.instance U _10WordDBInfo.instance U _11WordKeyInfo.instance 0000039c D _10WordDBInfo.instance U _11WordKeyInfo.instance U _14WordRecordInfo.instance U _11WordKeyInfo.instance 000008f8 D _11WordKeyInfo.instance U _10WordDBInfo.instance U _11WordKeyInfo.instance U _14WordRecordInfo.instance 00000870 D _11WordMonitor.instance 00000160 D _14WordRecordInfo.instance U _11WordKeyInfo.instance U _14WordRecordInfo.instance 00000988 D _8WordType.instance > nm test/testnet.o | grep instance > 5. Type > cp /bin/true test/testnet It was actually cp /usr/bin/true test/testnet > make check PASS: t_wordkey PASS: t_wordlist PASS: t_wordskip PASS: t_wordbitstream PASS: t_search PASS: t_htdb PASS: t_rdonly PASS: t_trunc PASS: t_url running htdig: expected http://localhost:7400/set1/ http://localhost:7400/set1/bad_local.htm http://localhost:7400/set1/script.html http://localhost:7400/set1/site%201.html http://localhost:7400/set1/site2.html http://localhost:7400/set1/site3.html http://localhost:7400/set1/site4.html http://localhost:7400/set1/sub%2520dir/ http://localhost:7400/set1/sub%2520dir/empty%20file.html http://localhost:7400/set1/title.html but got FAIL: t_htdig PASS: t_htsearch PASS: t_htmerge Could not fetch URL FAIL: t_htnet PASS: t_htdig_local PASS: t_factors PASS: t_fuzzy PASS: t_parsing PASS: t_templates PASS: t_validwords ==================== 2 of 19 tests failed ==================== gmake[1]: *** [check-TESTS] Error 1 gmake[1]: Leaving directory `/usr/src/WWW/htdig/htdig-3.2.0b6/test' gmake: *** [check-am] Error 2 > > Warnings from htdig: > > > > Warning: Configuration option heading_factor_1 is no longer supported > > Warning: Configuration option heading_factor_2 is no longer supported > > Warning: Configuration option heading_factor_3 is no longer supported > > Warning: Configuration option heading_factor_4 is no longer supported > > Warning: Configuration option heading_factor_5 is no longer supported > > Warning: Configuration option heading_factor_6 is no longer supported > > Warning: Configuration option modification_time_is_now is no longer supported > > Warning: Configuration option pdf_parser is no longer supported > > Warning: Configuration option translate_amp is no longer supported > > Warning: Configuration option translate_lt_gt is no longer supported > > Warning: Configuration option translate_quot is no longer supported > > > > Huh? > > Because people were confused by pdf_parser no longer working in > ht://Dig, it now checks for old 3.1.x configuration attributes which > are in the htdig.conf file but not supported by ht://Dig 3.2.x > Are any of these options specified in your htdig.conf? If not, this > is a bug... Thanks Lachlan; yes I had all those attributes from 3.1.x days left in my htdig.conf file. Regards, Joe -- _/ _/_/_/ _/ ____________ __o _/ _/ _/ _/ ______________ _-\<,_ _/ _/ _/_/_/ _/ _/ ......(_)/ (_) _/_/ oe _/ _/. _/_/ ah jj...@cl... |
|
From: Christopher M. <chr...@mc...> - 2004-06-10 03:39:02
|
On Wed, 2004-06-09 at 15:28, Joe R. Jah wrote: > It's a serious BUG;( That's what I thought. Thanks for the feedback. In my position, I'm fortunate that I have a php wrapper that is cleaning up all input before it is sent to htsearch, so I can write a little function that will strip these. However, it might be a good idea for the htdig team to let other folks who are currently using 3.2 in production about this as this makes it easy to cripple any machine running htdig 3.2 with boolean search feature. Cheers, Chris -- Christopher Murtagh Enterprise Systems Administrator ISR / Web Communications Group McGill University Montreal, Quebec Canada Tel.: (514) 398-3122 Fax: (514) 398-2017 |
|
From: Gabriele B. <an...@ti...> - 2004-06-09 22:31:43
|
Hi Gilles, At 22.10 09/06/2004, Gilles Detillieux wrote: >Just curious, but why did you need to manually apply my patch? Did it >not work with the patch command? The manual changes to conf_lexer.lxx >were OK, despite lots of changes to the indentation which now make it >harder to read (remember standard tab stops are 8 spaces), but you missed >one of my changes to conf_parser.yxx, which is likely to break things. No, it did not work. I had all the changes rejected. I tried to apply it against the latest CVS code. That's probably why I stuffed things up. However, I am sorry about the indentation problem, I had 4 spaces set. >It would be a shame to release yet another beta release and still not >have these problems fixed! Proper error handling has been lacking for >a long time, and many users have been confused by the config parser's >cryptic error messages. This will at least tell them what file to look >at, and the proper line number when using includes. The problem with >files then end without a newline has caught many people too. OK. I perfectly agree with you. That's why I asked people's opinion and I rely on yours very much. >this patch to go into b6, but it would be a good idea if a few other >developers tested it first, as I asked back in April. All I can say is >it works for me (but I tested it using flex 2.5.4a, and only on RH 9). You are right. I did not have a chance to try it before. However, tomorrow I will regenerate the conf_parser.cxx file and commit the changes, and prepare the new release tarball. If everything is fine, I will release 3.2.0b6 on friday morning Central Europe Time. Sounds good? Ciao and thanks, -Gabriele -- Gabriele Bartolini: Web Programmer, ht://Dig & IWA/HWG Member, ht://Check maintainer Current Location: Prato, Toscana, Italia an...@ti... | http://www.prato.linux.it/~gbartolini | ICQ#129221447 > "Leave every hope, ye who enter!", Dante Alighieri, Divine Comedy, The Inferno |
9 messages has been excluded from this view by a project administrator.
