From owner-freebsd-cvsweb@FreeBSD.ORG Fri Jun 27 09:06:50 2003 Return-Path: Delivered-To: freebsd-cvsweb@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 12AE137B401; Fri, 27 Jun 2003 09:06:50 -0700 (PDT) Received: from amsfep12-int.chello.nl (amsfep12-int.chello.nl [213.46.243.18]) by mx1.FreeBSD.org (Postfix) with ESMTP id B8CA043FCB; Fri, 27 Jun 2003 09:06:48 -0700 (PDT) (envelope-from ptok@iname.com) Received: from RDPAULG ([24.132.105.215]) by amsfep12-int.chello.nl (InterMail vM.5.01.05.17 201-253-122-126-117-20021021) with SMTP id <20030627160646.DDAI6336.amsfep12-int.chello.nl@RDPAULG>; Fri, 27 Jun 2003 18:06:46 +0200 Message-ID: <001401c33cc6$1b935f20$3201a8c0@medis.local> From: "paul gelderblom" To: , =?iso-8859-1?Q?Ville_Skytt=E4?= References: <20030626173300.ULK8361.mf1@mf1.bredband.net> Date: Fri, 27 Jun 2003 18:06:45 +0200 MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 6.00.2800.1158 X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1165 X-Mailman-Approved-At: Fri, 27 Jun 2003 09:41:58 -0700 cc: cvsweb@FreeBSD.org Subject: Re: Re: cvsweb and binary files X-BeenThere: freebsd-cvsweb@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: CVS Web maintenance mailing list [restricted posting] List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 27 Jun 2003 16:06:50 -0000 Daniel, others: Daniel wrote: > I also have a feature request. > It would be nice with a search function in cvsweb. > I did this as a separate cgi script but it would be more practical if it was > integrated into cvsweb. > Just run find -name from the current directory and parse the output to > get links back into cvsweb. I built that! Using File::find. It integrates with cvsweb (both ways: from cvsweb you can link to the search functionality, allowing searches starting in a certain directory, and from the search you get linked to the file in cvsweb) It also does: - content searches in RCS files or the latest revision (look for 'readme.*' files containing 'Known Bug') - regexes or just strings for the content match; - filename selection using wildcards patterns (*.cpp) or regexes - case sensitivity or not for both match types - selection based on edit status (watch on/off ; edited files) - selection based on file type (-kb -> binary ) and combinations of the above. However: - Due to the nature of it (blunt filesytem search) , it is a resource eater. Maintainers on public repositories may not want it installed! - I did not include taint checking (have only friendly users here). Thay may even be complex, due to the user-specified regexes. I do not think it should be integrated *in* CVSWEB since that is already complex enough: just integrate *with* cvswevb: crosslinks in both directions Anyhow, enough blabla: should I post it? Paul