Re: trouble with symlinks

[Simon Strandgaard]

I might have expressed my self wrong.
Its not the symlink it self, i store in my repository, its the symlinked
file.

I have only files in my repository, without any symlinks!
But i have many symlinks in the directory where i checked out my source
tree.

What im interested in having cvs to look at the timestamp of files those
which my links point to.
My problem is that cvs is looking at the symlinks timestamp.

I hope you getting my problem, any help is apreciated.

Regards
Simon Strandgaard
BTW. A 3th ugly solution could be to make hardlinks, jyex!!!



Art <address@hidden> skrev i en
nyhedsmeddelelse:address@hidden
> > -----Original Message-----
> > From: address@hidden [mailto:address@hidden Behalf Of
> > Simon Strandgaard
> > Sent: Monday, January 14, 2002 9:12 AM
> > To: address@hidden
> ...
> > I dont see why this should be unsafe?
> >
> > I know there are many oddities when storing symlinks inside cvs.
> > But i dont see why symlink pointing out of the repository to
> > outside files, should be a problem?  It works partly for me, except
> > that cvs look at the symlinks timestamps instead of the symliked-files.
> >
> > The freebsd man pages doesnt talk at all about symlinks. Where
> > can i find some info on symlinks and cvs?
> >
> > Well thanks, i couldnt find any earlier messages on google that
discussed
> > the subject, the only thing i saw where trouble with link residing
inside
> > the
> > repository.
> ...
> > BTW, I have made a ruby script that syncronizes the timestamps, so i can
> > commit.
>
> Well. You seem to have a workaround for what you see as a problem.
> Admittedly, I have only limited experience with CVS, however, I subscribe
> to the philosophy of TAR and other Unix utilities which percieve symlinks
> as metadata. So, they really are NOT part of the CVS repository if you
> stick them in there, other than to perform a purpose YOU deem necessary.
> As such, I would consider CVS to be working as designed and I would
consider
> any other behaviour to be YOUR responsibility, e.g., via triggers in CVS
or
> a layer you'd laid over it.