Binary files in CVS

Can someone comment on this? I didn't know CVS had a binary flag, but I
see it in the docs now.

---------------------------------------------------------------------------

Csaba Nagy wrote:

Hi all,

[Maybe this should go on hackers, but I'm not subscribed]
I've checked out some time ago the 7_3_STABLE CVS branch of the postgres
sources.
Having it done on a Linux box I had no problems with it.
However, I've made some changes, and imported the resulting sources in
my company's CVS repository. What I've noticed in the process is that
none of the binary files checked out from the postgres CVS repository
(gifs, tars) are marked as binary (with -kb). Am I doing something wrong
with the checkout ?
On our local repository I can import the files as binary, this is not
the issue, I just wonder if the postgres CVS repository is correctly set
up ?
Binary files handled as text could be a potential problem for somebody
checking out on a non-unix system.

Thanks,
Csaba.

---------------------------(end of broadcast)---------------------------
TIP 6: Have you searched our list archives?

http://archives.postgresql.org

-- 
  Bruce Momjian                        |  http://candle.pha.pa.us
  pgman@candle.pha.pa.us               |  (610) 359-1001
  +  If your life is a hard drive,     |  13 Roberts Road
  +  Christ can be your backup.        |  Newtown Square, Pennsylvania 19073

I found the following binary files:

./doc/src/graphics/catalogs.gif
./doc/src/graphics/clientserver.gif
./doc/src/graphics/connections.gif
./src/tools/backend/flow.gif

and marked them as you suggested using CVS.

---------------------------------------------------------------------------

Csaba Nagy wrote:

You can do it with the "cvs admin -kb __file_list__" command.

Cheers,
Csaba.

On Mon, 2003-06-02 at 21:56, Tom Lane wrote:

Bruce Momjian <pgman@candle.pha.pa.us> writes:

Can someone comment on this? I didn't know CVS had a binary flag, but I
see it in the docs now.

I believe the binary files *should* be marked -kb, but I don't know CVS
well enough to know how to fix the setting on an existing file.

regards, tom lane

-- 
  Bruce Momjian                        |  http://candle.pha.pa.us
  pgman@candle.pha.pa.us               |  (610) 359-1001
  +  If your life is a hard drive,     |  13 Roberts Road
  +  Christ can be your backup.        |  Newtown Square, Pennsylvania 19073

I have also found the following files to be binary:

contrib/spi/preprocessor/step1.e
doc/src/graphics/catalogs.cgm

The first one is OS specific, so I guess it will cause no problem if
it's not marked as binary, and it's not already corrupted. Note that the
binary flag is also useful to avoid CVS to do keyword substitutions
(like the $Id $ things). So if you get a binary file which contains by
some chance the string "$Id $", CVS will kindly substitute it for you
with the usual version/date stuff. This is why adding the binary flag is
recommended even if you don't want to go cross platform.

Cheers,
Csaba.

Csaba Nagy <nagy@ecircle-ag.com> writes:

I have also found the following files to be binary:
doc/src/graphics/catalogs.cgm

Good catch.

contrib/spi/preprocessor/step1.e

Hm. I do not think this should be in the distribution at all. It
appears to be a precompiled executable of step1.c in the same directory.
I propose removing it (and adjusting the comments in example.sql in
the same directory).

regards, tom lane