Re: how to support symlinks?
-Original Message- From: Frederic Brehm [EMAIL PROTECTED] Sent: Feb 18, 2004 5:27 PM To: [EMAIL PROTECTED] Subject: Re: how to support symlinks? At 04:58 PM 2/18/2004, Eric Siegerman wrote: a simple mechanism has been implemented Perhaps it is really, really simple: cat .symlinks | xargs ln -s - i can see that it's not a deep solution. but since that's the case, why did at least one person go to the trouble of once writing a script to handle it? tell you what -- to avoid wasting any more bandwidth, let's do this. if you off-hand happen to know of a pre-rolled script that's equivalent to the aforementioned symlinks, drop me a note offline with a pointer and i'll be amused to see how similar it is to the solution i already came up with. if you *don't* know of a pointer to such a script, please don't waste any more time by telling me that: a) CVS doesn't handle symlinks, or b) it's really, really simple in other words, if you don't know the answer to my *actual* question, just hit 'delete' and keep moving. fair? rday ___ Info-cvs mailing list [EMAIL PROTECTED] http://mail.gnu.org/mailman/listinfo/info-cvs
Re: how to support symlinks?
On Wed, 18 Feb 2004, Larry Jones wrote: Robert P. J. Day writes: does anyone have a copy of this, or whatever people have settled on as a common solution? Since my previous response was apparently not clear enough, the common solution is to create the symlinks as an integral part of your (presumably) existing build or install process. If you don't have an existing build or install process, then create one. On Unix-like systems, that typically involves ``make''; I can't speak for other systems. and since my previous query was apparently not clear enough, i *know* the philosophy behind the solution. i was asking for a reference/URL/pointer to a previous solution so that i could, in the great tradition of geeks everywhere, avoid re-inventing the wheel. mercifully, a couple people had more google luck than me and provided the locations. thanks muchly. rday ___ Info-cvs mailing list [EMAIL PROTECTED] http://mail.gnu.org/mailman/listinfo/info-cvs
Re: how to support symlinks?
Robert P. J. Day [EMAIL PROTECTED] writes: problem is, i don't know how to interpret the reference to the tarball. a 3-year old posting says to get the source from gnudist.gnu.org:/usr/local/src/symlinks-1.1.tar.gz. Probably means FTP, ie ftp://gnudist.gnu.org/usr/local/src/symlinks-1.1.tar.gz. But the file is not at that location. Sorry, I don't know where the current version is. -- Ed Avis [EMAIL PROTECTED] ___ Info-cvs mailing list [EMAIL PROTECTED] http://mail.gnu.org/mailman/listinfo/info-cvs
Re: how to support symlinks?
On Wed, 18 Feb 2004, Ed Avis wrote: Robert P. J. Day [EMAIL PROTECTED] writes: problem is, i don't know how to interpret the reference to the tarball. a 3-year old posting says to get the source from gnudist.gnu.org:/usr/local/src/symlinks-1.1.tar.gz. Probably means FTP, ie ftp://gnudist.gnu.org/usr/local/src/symlinks-1.1.tar.gz. But the file is not at that location. Sorry, I don't know where the current version is. my problem exactly. :-) given that this is a problem that hundreds before me have tripped over, i'm assuming there's a standard solution. i'm just trying to find it. rday ___ Info-cvs mailing list [EMAIL PROTECTED] http://mail.gnu.org/mailman/listinfo/info-cvs
Re: how to support symlinks?
Robert P. J. Day writes: my problem exactly. :-) given that this is a problem that hundreds before me have tripped over, i'm assuming there's a standard solution. The standard solution is to have the necessary symlinks created by the build (or install) process rather than trying to shoehorn that into the source control process. -Larry Jones That's the problem with nature. Something's always stinging you or oozing mucus on you. -- Calvin ___ Info-cvs mailing list [EMAIL PROTECTED] http://mail.gnu.org/mailman/listinfo/info-cvs
Re: how to support symlinks?
On Wed, 18 Feb 2004, Robert P. J. Day wrote: Probably means FTP, ie ftp://gnudist.gnu.org/usr/local/src/symlinks-1.1.tar.gz. But the file is not at that location. Sorry, I don't know where the current version is. my problem exactly. :-) given that this is a problem that hundreds before me have tripped over, i'm assuming there's a standard solution. i'm just trying to find it. Meta-CVS supports symlinks. You can ``mcvs add'' a symlink under version control, or use ``mcvs ln'' to create one. You can move or rename them with ``mcvs mv'' just like files, and likewise remove them with ``mcvs rm''. Symlinks appear, disappear, move or retarget as needed when you fetch versions with ``mcvs up''. ___ Info-cvs mailing list [EMAIL PROTECTED] http://mail.gnu.org/mailman/listinfo/info-cvs
Re: how to support symlinks?
On Wed, 18 Feb 2004, Larry Jones wrote: Robert P. J. Day writes: my problem exactly. :-) given that this is a problem that hundreds before me have tripped over, i'm assuming there's a standard solution. The standard solution is to have the necessary symlinks created by the build (or install) process rather than trying to shoehorn that into the source control process. i *know* that. in a previous post, i referred to a utility i read about in a 3-year-old posting called symlinks that uses a .symlinks file in each directory that will contain symlinks. it sounds like what i'm after, and i just wanted a pointer to the utility -- googling didn't turn up its current location. does anyone have a copy of this, or whatever people have settled on as a common solution? rday ___ Info-cvs mailing list [EMAIL PROTECTED] http://mail.gnu.org/mailman/listinfo/info-cvs
Re: how to support symlinks?
On Wed, 18 Feb 2004, Kaz Kylheku wrote: On Wed, 18 Feb 2004, Robert P. J. Day wrote: Probably means FTP, ie ftp://gnudist.gnu.org/usr/local/src/symlinks-1.1.tar.gz. But the file is not at that location. Sorry, I don't know where the current version is. my problem exactly. :-) given that this is a problem that hundreds before me have tripped over, i'm assuming there's a standard solution. i'm just trying to find it. Meta-CVS supports symlinks. You can ``mcvs add'' a symlink under version control, or use ``mcvs ln'' to create one. You can move or rename them with ``mcvs mv'' just like files, and likewise remove them with ``mcvs rm''. Symlinks appear, disappear, move or retarget as needed when you fetch versions with ``mcvs up''. meta-cvs is not a possible solution, since we need web-page access to the repository as well, and as i read it, meta-cvs doesn't handle that. and it's not like i'm going to adopt an entirely new tool just for something as trivial as symlinks. symlinks. that's all i want. really. rday ___ Info-cvs mailing list [EMAIL PROTECTED] http://mail.gnu.org/mailman/listinfo/info-cvs
Re: how to support symlinks?
Robert P. J. Day wrote: meta-cvs is not a possible solution, since we need web-page access to the repository as well, and as i read it, meta-cvs doesn't handle that. and it's not like i'm going to adopt an entirely new tool just for something as trivial as symlinks. symlinks. that's all i want. really. Googling for GNU symlinks and clicking I'm feeling lucky takes me to the following page: http://packages.debian.org/unstable/utils/symlinks At the bottom of that page is a working link to the source code as well as to several flavors of binary. Is that what you're looking for? A bit more google-fu also turned up the following, which might be useful in your situation: http://bre.klaki.net/programs/cvs-symlinks/ HTH, Geoff ___ Info-cvs mailing list [EMAIL PROTECTED] http://mail.gnu.org/mailman/listinfo/info-cvs
Re: how to support symlinks?
Ok, you've got me curious. On Wed, Feb 18, 2004 at 04:06:29PM -0500, Robert P. J. Day wrote: [...] a utility i read about in a 3-year-old posting called symlinks that uses a .symlinks file in each directory that will contain symlinks. This seems to be the original reference to it: http://www.gnu.org/server/standards/README.html#SEC01 Reading between the lines, I infer that the symlinks program was developed as an internal utility for the GNU web site. Perhaps it was never formally released to the public. That seems a bit surprising, for the FSF of all people, but it's not actually contrary to the GPL :-) Maybe the program was never deemed to be of release quality. Clues: - The wording, a simple mechanism has been implemented on the machine hosting the www.gnu.org, suggests a quick-and-dirty local utility - The file's location is given as: gnudist.gnu.org:/usr/local/src/symlinks-1.1.tar.gz which is an rcp-style pathname, not a URL - The directory part of that location is /usr/local/src, not a directory one usually finds in anon-ftp areas -- and certainly not one I recall ever seeing on ftp.gnu.org (which has the same IP address as gnudist, btw) Try asking the GNU webmasters, or other individuals who've discussed the thing in the past. -- | | /\ |-_|/ Eric Siegerman, Toronto, Ont.[EMAIL PROTECTED] | | / It must be said that they would have sounded better if the singer wouldn't throw his fellow band members to the ground and toss the drum kit around during songs. - Patrick Lenneau ___ Info-cvs mailing list [EMAIL PROTECTED] http://mail.gnu.org/mailman/listinfo/info-cvs
Re: how to support symlinks?
Robert P. J. Day writes: does anyone have a copy of this, or whatever people have settled on as a common solution? Since my previous response was apparently not clear enough, the common solution is to create the symlinks as an integral part of your (presumably) existing build or install process. If you don't have an existing build or install process, then create one. On Unix-like systems, that typically involves ``make''; I can't speak for other systems. -Larry Jones I've got more brains than I know what to do with. -- Calvin ___ Info-cvs mailing list [EMAIL PROTECTED] http://mail.gnu.org/mailman/listinfo/info-cvs
Re: how to support symlinks?
At 05:27 PM 2/18/2004, Frederic Brehm wrote: Perhaps it is really, really simple: cat .symlinks | xargs ln -s I should never do this just before leaving for home. :-( That won't work. This has a better chance #! /bin/bash for file in $(cat .symlinks); do ln -s $file . done The rest is left as an exercise for the reader. Good night, Fred ___ Frederic W. Brehm, Sarnoff Corporation, http://www.sarnoff.com/ ___ Info-cvs mailing list [EMAIL PROTECTED] http://mail.gnu.org/mailman/listinfo/info-cvs
Re: how to support symlinks?
At 04:58 PM 2/18/2004, Eric Siegerman wrote: a simple mechanism has been implemented Perhaps it is really, really simple: cat .symlinks | xargs ln -s Fred ___ Frederic W. Brehm, Sarnoff Corporation, http://www.sarnoff.com/ ___ Info-cvs mailing list [EMAIL PROTECTED] http://mail.gnu.org/mailman/listinfo/info-cvs
how to support symlinks?
yes, i've done the google searching, and found at least one reference to a symlinks script that works with a .symlinks file in a directory to support symlinks under CVS. problem is, i don't know how to interpret the reference to the tarball. a 3-year old posting says to get the source from gnudist.gnu.org:/usr/local/src/symlinks-1.1.tar.gz. i get the impression that this a reference to GNU's savannah repository, but can someone point me at the latest version of this utility? thanks. rday ___ Info-cvs mailing list [EMAIL PROTECTED] http://mail.gnu.org/mailman/listinfo/info-cvs
