-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
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
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.
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
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
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
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
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.
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.
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:
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
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
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/
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
14 matches
Mail list logo
