My proposal is to use an editor that is aware of DOS and UNIX line
endings.
- Altu
-----Original Message-----
From: Ramon Ribó <ram...@compassis.com>
To: fossil-users@lists.fossil-scm.org
Sent: __aolWsbDateToL10n__Wed, 21 Oct 2009 16:36:47
+0200__aolWsbDateToL10n__
Subject: Re: [fossil-users] Developing on Unix and Windows
Hello,
The conversion of line endings does not affect at all to its sha1
checksum
as it is only an input/output filter. The internal representation of
the file inside
fossil continues to be unique.
Some files need conversion and some other no. In cvs, when adding a
file
it is necessary to specify for every file if it is ascii or not. This
property is stored
with the file. An alternative could be that the user defined some
extensions that
need filtering. For example:
fossil settings ascii-extensions .tcl .c .cc
The problem is that, if fossil does not provide some facility for
this, it is very
difficult or impossible to implement the solution externally to fossil
as an script
or something.
In any case, what is your proposal for using fossil to manage a
program
both in unix and windows?
2009/10/21 D. Richard Hipp <d...@hwaci.com>:
>
> On Oct 21, 2009, at 7:57 AM, Ramon Ribó wrote:
>
>> Hello,
>>
>> When developing the same program on Unix and on Windows, cvs
>> automatically converts the line
>> end of the files to the appropriates for every platform. In this way,
>> if we commit a file in windows that
>> contains "\r\n" as line ends, we can checkout this file on unix and
it
>> will have "\n" line ends.
>>
>> As I see, fossil does not change the line endings of the ascii
>> files. If we try to work as is, I see several
>> problems, for example, scripts begin with "#!" on unix do not work if
>> they have "\r\n" as line end"
>>
>> What is the opinion of the fossil users & developers on this? What
>> is the suggested method for developing
>> the same program in both unix and windows? will fossil be modified in
>> the future to contain an automatic
>> translation of line endings?
>
>
> Fossil was designed with file integrity in mind. The identifier for a
> file is its SHA1 checksum. If you start changing line-endings, that
> changes the SHA1 checksum, and the identity of the file.
>
> Furthermore, some file formats are broken by changing line endings.
> Certainly most binary file formats (GIFs, JPEGs) cannot tolerate line-
> ending changes. But even some text formats (for example the fossil
> manifest file) require a specific line ending.
>
>
> D. Richard Hipp
> d...@hwaci.com
>
>
>
> _______________________________________________
> fossil-users mailing list
> fossil-users@lists.fossil-scm.org
> http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users
>
_______________________________________________
fossil-users mailing list
fossil-users@lists.fossil-scm.org
http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users
_______________________________________________
fossil-users mailing list
fossil-users@lists.fossil-scm.org
http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users
