Re: Issues retaining a DOS' file encoding when committing it into a UNIX reposi

>
> Hi Hector,
>
> > When you say set the correct line separators using a
> > script, could you give me some more detail.
>
> Well, are you sure you need different line separators in the working copy? Or
> do you need them only in the "output of the working copy", e.g. packages for
> different operating systems? If the latter case, then changing the line
> separators in the build script (e.g. ANT) would be the best solution.
>
> > I've looked at SVN && SmartSVN but was disappointed with the way tags are
> > handled. A copy of the repository every time it gets tagged is too costly.
>
> Copying in SVN costs nearly nothing. It is quite similar to hard links in the
> Unix world.
>
> --
> Best regards,
> Thomas Singer
> _____________
> syntevo GmbH
> http://www.syntevo.com
>
>
> "hectorub" <hurdaneta@...> wrote:
>
> > Hi Thomas,
> >
> > Thanks for the reply. When you say set the correct line separators using a
> > script, could you give me some more detail.
> >
> > I've looked at SVN && SmartSVN but was disappointed with the way tags are
> > handled. A copy of the repository every time it gets tagged is too costly. Or
> > is my understanding incorrect?
> >
> > Thanks
> > Hector Urdaneta
> >
> >
> >
> >
> > --- In smartcvs@..., syntevo Support <smartcvs@> wrote:
> > >
> > > Hi Hector,
> > >
> > > > When I commit DOS files
> > > > into the repository I see that the ,v files gets saved in UNIX format.
> > >
> > > You should not worry about how file content is stored in the ,v files, because
> > > this is CVS server internal. SmartCVS always converts the line separators to
> > > the correct line separator for the repository (\n), just like any other
> > > correctly working CVS client.
> > >
> > > > So in short, what do I need to do to ensure that DOS text files get committed
> > > > into a UNIX repository from a UNIX client in its original DOS format, and that
> > > > when I retrieve it on a UNIX OS, its DOS format is preserved?
> > >
> > > You only can define what line separator to use for your whole project
> > > (Project|Settings, Text File Options). You can't define that on a per-file
> > > base using CVS. If you need that, then you should use (Smart)SVN or set the
> > > correct line separators locally using a script.
> > >
> > > --
> > > Best regards,
> > > Thomas Singer
> > > _____________
> > > syntevo GmbH
> > > http://www.syntevo.com
> > >
> > >
> > > "hectorub" <hurdaneta@> wrote:
> > >
> > > > Hi,
> > > >
> > > > I'm having trouble committing DOS text files into a UNIX repository. By UNIX
> > > > repository I mean one that is stored on a UNIX box. When I commit DOS files
> > > > into the repository I see that the ,v files gets saved in UNIX format. I'm
> > > > running the smartCVS (professional) client from a Linux machine.
> > > >
> > > > My working copy of the repository contains a mix of DOS and UNIX files. Not
> > > > knowingly, I originally committed all files into the repository with the Text
> > > > File Encoding in the Repository in ASCII mode. I later on changed the setting
> > > > to Unicode (UTF-8). Removed the DOS files from the repository and tried
> > > > committing them once again to the repository. When I look at the ,v file in
> > > > the repository I still see that the files are stored in the UNIX format.
> > > >
> > > > So in short, what do I need to do to ensure that DOS text files get committed
> > > > into a UNIX repository from a UNIX client in its original DOS format, and that
> > > > when I retrieve it on a UNIX OS, its DOS format is preserved?
> > > >
> > > > Thanks in advance for any help
> > > > Hector Urdaneta
> > > > Linear Technology Corporation
> > >
> >
> >
> >
> >
> > ------------------------------------
> >
> > Yahoo! Groups Links
> >
> >
> >
> >
>