[cvsnt] Workaround for 260 char limitation?

Stefan Cordes stefan.cordes.rsc at googlemail.com
Wed Nov 18 09:14:22 GMT 2009


Hi!
My client environment is
C:\>cvs -version
Concurrent Versions System (CVSNT) 2.5.03 (Scorpio) Build 2382
(client/server)

The Server environment I do not know.

When accessing the repository via Eclipse 3.4.2 I do not have any problems
with the long file names.

My intention is to use the cvs repository with maven goals like scm:prepare
to automatically assign a label.
Our Maven 1.0.2 just delegates the scm commands to my local cvs.exe which is
the one from CVSNT above.

I tried the CVS Implementation from cygwin but that one could not
authenticate to our cvs Server (maybe due to missing configuration on my
client side).

I even tried the evs (cvsnt 3.x open source), but that one had other errors
which I do not exactly remember now.

Best regards,
Stefan

On Thu, Nov 5, 2009 at 4:38 PM, <pdfeeny at aep.com> wrote:

> cvsnt-bounces at cvsnt.org wrote on 11/05/2009 10:28:36 AM:
>
> > Hi!
> > Is there a workaround to avoid
> >
>
> http://customer.march-hare.com/webtools/bugzilla/ttshow_bug.cgi?tt=1&id=5629
> > when trying to "cvs update" a project that has path-names longer than
> 260
> > chars?
>
> Nope.  This is due to Microsoft's implementation of the NTFS filesystem
> (remember how we'd never need more than 640K of memory?)and is built into
> the filesystem (Microsoft's limit is actually 254 character from drive
> designator to last character of file extension).
>
> You don't mention your server/client setup as that would determine the
> impact
> to your environment.
>
> Paul Feeny
>
>
> > _______________________________________________
> > cvsnt mailing list
> > cvsnt at cvsnt.org
> > http://www.cvsnt.org/cgi-bin/mailman/listinfo/cvsnt
> >
> > Upgrade to CVS Suite for more features and support: http://march-
> > hare.com/cvsnt/
>
>


More information about the cvsnt mailing list