X-Original-To: pgsql-www-postgresql.org@localhost.postgresql.org Received: from localhost (av.hub.org [200.46.204.144]) by svr1.postgresql.org (Postfix) with ESMTP id 67359D9501 for ; Wed, 21 Sep 2005 06:50:29 -0300 (ADT) Received: from svr1.postgresql.org ([200.46.204.71]) by localhost (av.hub.org [200.46.204.144]) (amavisd-new, port 10024) with ESMTP id 37321-10 for ; Wed, 21 Sep 2005 09:50:25 +0000 (GMT) Received: from anchor-post-31.mail.demon.net (anchor-post-31.mail.demon.net [194.217.242.89]) by svr1.postgresql.org (Postfix) with ESMTP id 3C847D70A7 for ; Wed, 21 Sep 2005 06:50:25 -0300 (ADT) Received: from mailgate.vale-housing.co.uk ([194.217.48.34] helo=vale-housing.co.uk) by anchor-post-31.mail.demon.net with esmtp (Exim 4.42) id 1EI19X-0005dJ-49 for pgsql-www@postgresql.org; Wed, 21 Sep 2005 09:44:35 +0000 X-MimeOLE: Produced By Microsoft Exchange V6.5.7226.0 Content-class: urn:content-classes:message MIME-Version: 1.0 Content-Type: multipart/alternative; boundary="----_=_NextPart_001_01C5BE91.E49494F9" Subject: Re: PGDN and CVS Date: Wed, 21 Sep 2005 10:50:25 +0100 Message-ID: X-MS-Has-Attach: X-MS-TNEF-Correlator: Thread-Topic: PGDN and CVS Thread-Index: AcW+kIcT6CwluUdAQASZMbpU/xojqAAAHbZA From: "Dave Page" To: "Gevik babakhani" , X-Virus-Scanned: by amavisd-new at hub.org X-Spam-Status: No, hits=0.054 required=5 tests=[AWL=0.053, HTML_MESSAGE=0.001] X-Spam-Level: X-Archive-Number: 200509/49 X-Sequence-Number: 8563 This is a multi-part message in MIME format. ------_=_NextPart_001_01C5BE91.E49494F9 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable =20 ________________________________ From: Gevik babakhani [mailto:gevik@xs4all.nl]=20 Sent: 21 September 2005 10:41 To: pgsql-www@postgresql.org Cc: Dave Page Subject: PGDN and CVS =09 =09 Hi Dave, =20 Hi Gevik, =20 Regarding the PGDN. =20 1. Let's say we produce a directory with all kinds of static html,images sample sql scripts etc... How do we want to update the whole PGDN within our CVS. =20 =20 We need a script that will traverse the directory structure and perform the appropriate CVS add/remove operations based on what it finds, and then commits the whole tree. It sounds hard at first thought, but I don't think it is when thought about further - for example, we hierarchically traverse the tree, and for each directory or file we find, we check CVS/Entries to see if it exists in CVS. If not, we do a CVS ADD on it. When we've processed the files, we then go line by line through CVS/Entries, and CVS REMOVE any files or directories that don't exist any more. That should be a relatively trivial perl script for someone familiar with perl. =20 1. Do we want to put the static PGDN files in CVS anyway? Should we keep the PGDN files separate not mixing with the current site's CVS?=20 =20 Yes, we do want them in CVS because we build the entire from there & the backend database. we don't want to start pulling in content from additional places as that just makes it much harder to rebuild the servers if there is ever a problem. =20 Regards, Dave. ------_=_NextPart_001_01C5BE91.E49494F9 Content-Type: text/html; charset="us-ascii" Content-Transfer-Encoding: quoted-printable

From: Gevik babakhani = [mailto:gevik@xs4all.nl]=20
Sent: 21 September 2005 10:41
To:=20 pgsql-www@postgresql.org
Cc: Dave Page
Subject: = PGDN and=20 CVS

Hi=20 Dave,

Hi Gevik,

Regarding the=20 PGDN.

Let’s say we=20 produce a directory with all kinds of static html,images sample sql = scripts=20 etc… How do we want to update the whole PGDN within our=20 CVS.

We need a script=20 that will traverse the directory structure and perform the appropriate = CVS=20 add/remove operations based on what it finds, and then commits the whole = tree.=20 It sounds hard at first thought, but I don't think it is when thought = about=20 further - for example, we hierarchically traverse the tree, and for each = directory or file we find, we check CVS/Entries to see if it exists in = CVS. If=20 not, we do a CVS ADD on it. When we've processed the files, we then go = line by=20 line through CVS/Entries, and CVS REMOVE any files or directories that = don't=20 exist any more. That should be a relatively trivial perl script for = someone=20 familiar with perl.

Do we = want to put=20 the static PGDN files in CVS anyway? Should we keep the PGDN files = separate=20 not mixing with the current site’s = CVS?

Yes, we do want them in CVS because we build = the entire=20 from there & the backend database. we don't want to start pulling in = content=20 from additional places as that just makes it much harder to rebuild the = servers=20 if there is ever a problem.

Regards,=20 Dave.

------_=_NextPart_001_01C5BE91.E49494F9--