| Shared Workspace between Windows and Linux [message #144967] |
Tue, 24 February 2004 11:13  |
Eclipse User |
|
|
|
Howdy,
Is it possible, inadvisable or impossible to share a
workspace with java projects between a windows and a linux
box using rsync.
Transferring the files isn't a worry, but are there are
likely to be any gotchas?
TIA
Rich
|
|
|
|
|
| Re: Shared Workspace between Windows and Linux [message #145199 is a reply to message #145190] |
Wed, 25 February 2004 08:15  |
| Eclipse User |
|
|
|
rich boakes wrote:
>
>> In theory I think it is supposed to be possible...[snip similar]
>>
>> HTH,
>> Eric
>
>
> thx. that's enough to make the attempt worthwhile.
> r.
I think you will have a major problem though ..
Carriage returns are not the same on windows and linux.
On linux, there is only one character (ascii 0x0A or 10) when there are
two on windows (ascii 0x0A or 10 followed by ascii 0x0D or 13)
What it means is that if you want, for instance, to share your project
on a CVS repository, you will have major problems when comparing the
content of your files against the distant repository:
If you commit a file under windows, it will have two characters at the
end of each line.
Then you work on this file under linux and you decide to commit the
modifications.
The cvs content comparison editor will find an error on each line (will
find an additional character on each line - ascii 0x0D or 13)
You will encounter the same problem if you switch from windows to linux
(or the contrary) by copying the whole local repository from windows to
linux (or the contrary) instead of checkouting the whole repository in
an empty project directory.
Thus, I can only strongly advise you not to try this if you do not want
to spend a long time trying to fix the broken files afterward. (I did it
and it is painful)
Hope this help,
Jean
--
"No brain, no headache"
|
|
|
| Re: Shared Workspace between Windows and Linux [message #145215 is a reply to message #145199] |
Wed, 25 February 2004 10:39 |
| Eclipse User |
|
|
|
Originally posted by: eclipse-user.jibeinc.com
Jean Couillaud wrote:
> I think you will have a major problem though .. Carriage returns are
> not the same on windows and linux. On linux, there is only one
> character (ascii 0x0A or 10) when there are two on windows (ascii
> 0x0A or 10 followed by ascii 0x0D or 13) What it means is that if you
> want, for instance, to share your project on a CVS repository, you
> will have major problems when comparing the content of your files
> against the distant repository: If you commit a file under windows,
> it will have two characters at the end of each line. Then you work on
> this file under linux and you decide to commit the modifications. The
> cvs content comparison editor will find an error on each line (will
> find an additional character on each line - ascii 0x0D or 13)
No, CVS takes care of that for you. From Chapter 9 of the CVS manual:
> 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).
That is why binary files have to be marked appropriately when committing
them to cvs - so it does not do the line-end conversion for such files.
Not to say there aren't problems trying to share an Eclipse repository
between windoze and Linux - just that CVS doesn't contribute to those
problems as you describe.
Eric
--
Eric Rizzo
Software Architect
Jibe, Inc.
http://www.jibeinc.com
|
|
|
| Re: Shared Workspace between Windows and Linux [message #145222 is a reply to message #145215] |
Wed, 25 February 2004 11:04 |
| Eclipse User |
|
|
|
Originally posted by: henning_sprang.gmx.de
Hy
Eric Rizzo wrote:
> Jean Couillaud wrote:
> > I think you will have a major problem though .. Carriage returns are
> > not the same on windows and linux. On linux, there is only one
> > character (ascii 0x0A or 10) when there are two on windows (ascii
> > 0x0A or 10 followed by ascii 0x0D or 13) What it means is that if you
> > want, for instance, to share your project on a CVS repository, you
> > will have major problems when comparing the content of your files
> > against the distant repository: If you commit a file under windows,
> > it will have two characters at the end of each line. Then you work on
> > this file under linux and you decide to commit the modifications. The
> > cvs content comparison editor will find an error on each line (will
> > find an additional character on each line - ascii 0x0D or 13)
> No, CVS takes care of that for you. From Chapter 9 of the CVS manual:
> > 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).
> That is why binary files have to be marked appropriately when committing
> them to cvs - so it does not do the line-end conversion for such files.
yes, but he's not going to share the files via CVS, but he wants to use
exact copies of the files, transferred via rsync.
If rcsync doesn't take care of the carraige return translation, he will
get lots of trouble when he'y starting to check dos files back into cvs
from linux,
exactly because the feature you mentioned you will end up in a real mess
of crippled textfiles with variuos different types of carraiage returns
mixed together in one file.
Diff's will stop working, too, if you compare dos files under linux with
"correct" files from cvs...
by the way: if you're using cvs, why don't just check out a sandbox on the
windows as well as on the linux machine? That's really the best solution...
Henning
|
|
|
| Re: Shared Workspace between Windows and Linux [message #146743 is a reply to message #145222] |
Sat, 28 February 2004 15:56 |
| Eclipse User |
|
|
|
Originally posted by: wagner.stefan.berlin.de
Hi,
Henning Sprang wrote:
> Eric Rizzo wrote:
>>Jean Couillaud wrote:
>>
>>>I think you will have a major problem though .. Carriage returns are
>>>not the same on windows and linux. On linux, there is only one
>>>...
> If rcsync doesn't take care of the carraige return translation, he will
> get lots of trouble when he'y starting to check dos files back into cvs
> from linux,
I used the same files at home (linux) and on work (win2k), and moved the
source with an usb-stick.
I had problems in the beginning, but when I told both editors to set the
encoding to 'Latin 1', and 'Latin 1' as default, my problems where solved.
I didn't do any conversion between reading or writing to my stick, so I
can imagine, rsync - which I don't know - will work too.
|
|
|
Powered by
FUDForum. Page generated in 0.36378 seconds
Home