RE: [Squirrel-sql-develop] CVS

[Colin B. <Col...@as...>]

Hi Patrick,

I ran those two scripts last night and it fell over with a class not found
error on one of the ant classes. org.apache....Main. I checked the scripts,
found the jar ant.jar and tried to unzip it and got a corrupt zip error.

There is an issue with uploading binary files as text. Take a look at
http://www.cvshome.org/docs/manual/cvs_9.html#SEC80


This is the relevant portion of the doc:

===============

There are two issues with using CVS to store binary files. The first is that
CVS by default converts line endings between the canonical form in which
they are stored in the repository (linefeed only), and the form appropriate
to the operating system in use on the client (for example, carriage return
followed by line feed for Windows NT).

The second is that a binary file might happen to contain data which looks
like a keyword (see section 12. Keyword substitution), so keyword expansion
must be turned off.

The `-kb' option available with some CVS commands insures that neither line
ending conversion nor keyword expansion will be done.

Here is an example of how you can create a new file using the `-kb' flag:

 

$ echo '$Id$' > kotest
$ cvs add -kb -m"A test file" kotest
$ cvs ci -m"First checkin; contains a keyword" kotest

If a file accidentally gets added without `-kb', one can use the cvs admin
command to recover. For example:

 

$ echo '$Id$' > kotest
$ cvs add -m"A test file" kotest
$ cvs ci -m"First checkin; contains a keyword" kotest
$ cvs admin -kb kotest
$ cvs update -A kotest
# For non-unix systems:
# Copy in a good copy of the file from outside CVS
$ cvs commit -m "make it binary" kotest

When you check in the file `kotest' the file is not preserved as a binary
file, because you did not check it in as a binary file. The cvs admin -kb
command sets the default keyword substitution method for this file, but it
does not alter the working copy of the file that you have. If you need to
cope with line endings (that is, you are using CVS on a non-unix system),
then you need to check in a new copy of the file, as shown by the cvs commit
command above. On unix, the cvs update -A command suffices.

==================

Col

-----Original Message-----
From: Patrick Lacson [mailto:pa...@la...]
Sent: Thursday, 22 November 2001 10:11
To: Colin Bell
Cc: Squirrel Developers List (E-mail)
Subject: Re: [Squirrel-sql-develop] CVS


Colin,

Hmm.. checked in as text shouldn't matter.  From your win32 box try the
following once you've done a fresh checkout of the module 'squirrel'

c:\cvs\squirrel>configure.bat

c:\cvs\squirrel>build.bat dist

Try those two commands which should configure your environment and build
a distribution.. (It works on my unix box and win32 box).  I personally
don't use the default cmd.exe shell provided with win32, I use cygwin
which emulates a unix shell on my win32 environment.  In any event,
that's whole nother can of worms..

Try that and tell me exactly what happens despite the CVS warnings that
you get..

-P


Colin Bell wrote:
> 
> Hi Patrick,
> 
> No I wasn't. I sent you an email from home last night but it hasn't got to
> the list yet - Bloody ISP! (or just possibly I forget to actually send
it).
> 
> I wasn't able to build as all the binary files seem to have gone up as
text
> (jars, gifs etc.) I'm new to CVS so bear with me while I ask some stupid
> questions. Is this anything to do with the way I checked the module out?
I'm
> using WinCVS and it did a good job of recognising the different file types
> when I did the original import and checking them back out just seemed to
> work but now that you've done an import from a different OS are we having
> some kind of file compatability problem?
> 
> Col
> 
> -----Original Message-----
> From: Patrick Lacson [mailto:pa...@la...]
> Sent: Thursday, 22 November 2001 9:47
> Cc: Squirrel Developers List (E-mail)
> Subject: Re: [Squirrel-sql-develop] CVS
> 
> Were you able to get the program to build?  the squirrel module builds
> properly.  I commented out the plugins from the installer since it was
> not properly working.  Other, than that it builds ok.  (see
> src/resources/izpack/izpack-complete-buildmagic.xml)
> 
> -P
> 
> Colin Bell wrote:
> >
> > Hi Patrick,
> >
> > Until we get the BuildMagic process sorted out I'll just keep using the
> > squirrel-sql module and I will manually synch them up later.
> >
> > If anybody else wants to use CVS you can put your plugin code up in
> > squirrel-sql/plugins/<plugin_internal_name> but just remember that
you'll
> > need to copy it over to the new module later.
> >
> > Col
> >
> > _______________________________________________
> > Squirrel-sql-develop mailing list
> > Squ...@li...
> > https://lists.sourceforge.net/lists/listinfo/squirrel-sql-develop
> 
> _______________________________________________
> Squirrel-sql-develop mailing list
> Squ...@li...
> https://lists.sourceforge.net/lists/listinfo/squirrel-sql-develop
> 
> _______________________________________________
> Squirrel-sql-develop mailing list

> Squ...@li...
> https://lists.sourceforge.net/lists/listinfo/squirrel-sql-develop