Re: TODO: Rename some /contrib modules from pg* to pg_*

From: "Andrew Dunstan" <andrew(at)dunslane(dot)net>
To: <scrappy(at)postgresql(dot)org>
Cc: <tgl(at)sss(dot)pgh(dot)pa(dot)us>, <jd(at)commandprompt(dot)com>, <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: TODO: Rename some /contrib modules from pg* to pg_*
Date: 2006-06-08 22:42:46
Message-ID: 3597.24.211.165.134.1149806566.squirrel@www.dunslane.net
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

Marc G. Fournier said:
> On Thu, 8 Jun 2006, Tom Lane wrote:
>
>> "Joshua D. Drake" <jd(at)commandprompt(dot)com> writes:
>>> 1. Fix makefiles so that contrib modules such as pgcrypto are not
>>> pg_crypto 2. Move directories to reflect above
>>> 3. Fix source and makefiles within sub project directories to create
>>> binaries and libs with correct output.. thus libpgcrypto.so.0.0 would
>>> become libpg_crypto.so.0.0
>>
>> That will lose the CVS history of the modules
>
> Umm, if co-ordinated with me, I can make the name changes at the file
> system level, so that history isn't lost ..
>

Renaming directories is nasty in CVS no matter which way you look at it - it
is one of the known bad limitations. You might preserve the history but you
could also break every existing repo copy. See
http://ximbiot.com/cvs/manual/cvs-1.11.15/cvs_7.html#SEC74

Unless there is a *very* good reason this should be avoided.

cheers

andrew

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Tom Lane 2006-06-08 22:47:13 Re: TODO: Determine optimal fdatasync/fsync, O_SYNC/O_DSYNC options
Previous Message Joshua D. Drake 2006-06-08 22:40:50 TODO: Determine optimal fdatasync/fsync, O_SYNC/O_DSYNC options