Hello Paul,
* Paul Eggert wrote on Wed, Oct 11, 2006 at 08:25:27PM CEST:
>
> [...] perhaps
> we should have two options, --copy-preserve and --copy. However, it
> won't be a problem for me (I don't use --copy) and it won't be a
> problem for Bruno (he does a make distclean after a bootstrap). W
>> Symlinks pass through the last-modified time of the gnulib files.
>> cp -p also passes through the last-modified time of the gnulib files.
>> So if the first "make" already sees the new files from the gnulib
>> tree through the symlinks, it will also see the new files from
>> the gnulib files th
Paul Eggert wrote:
> That being said, if there are strong feelings that "cp -p" is bad, I
> can change it to use "cp". After all, I won't be using the --copy
> option anyway, so it doesn't matter much to me what --copy does.
> Perhaps Bruno has an opinion?
I always use "make distclean" before (or
* Paul Eggert wrote on Wed, Oct 11, 2006 at 08:49:33AM CEST:
> > From: Ralf Wildenhues <[EMAIL PROTECTED]>
> >
> > > Yes, but exactly the same problem exists with symbolic links.
> >
> > I don't see how. The first `make' already sees the new files from the
> > gnulib tree, through the symlinks.
> Date: Wed, 11 Oct 2006 08:43:14 +0200
> From: Ralf Wildenhues <[EMAIL PROTECTED]>
>
> > Yes, but exactly the same problem exists with symbolic links.
>
> I don't see how. The first `make' already sees the new files from the
> gnulib tree, through the symlinks.
Symlinks pass through the last-m
* Paul Eggert wrote on Wed, Oct 11, 2006 at 08:32:53AM CEST:
> Ralf Wildenhues <[EMAIL PROTECTED]> writes:
>
> > Assume the first `make' causes some
> > object files to be updated, say, because of a previous `make clean',
> > or simply because they were out of date. Those object files will then
>
Ralf Wildenhues <[EMAIL PROTECTED]> writes:
> Argh, it was incomplete, sorry. Assume the first `make' causes some
> object files to be updated, say, because of a previous `make clean',
> or simply because they were out of date. Those object files will then
> have a timestamp that is newer than t
* Paul Eggert wrote on Wed, Oct 11, 2006 at 01:52:27AM CEST:
> Ralf Wildenhues <[EMAIL PROTECTED]> writes:
>
> > A failure case with `cp -p':
> > cd gnulib && cvs up
> > cd .../coreutils && make && ./bootstrap && make
>
> I don't understand this failure case. "cvs up" modifies the
> time sta
Ralf Wildenhues <[EMAIL PROTECTED]> writes:
> A failure case with `cp -p':
> cd gnulib && cvs up
> cd .../coreutils && make && ./bootstrap && make
I don't understand this failure case. "cvs up" modifies the
time stamps to the current date, and "cp -p" will copy
the modified time stamps, so i
* Ralf Wildenhues wrote on Tue, Oct 10, 2006 at 11:43:50PM CEST:
> A failure case with `cp':
with `cp -p' of course. Sorry about that.
> cd gnulib && cvs up
> cd .../coreutils && make && ./bootstrap && make
Hello Paul,
* Paul Eggert wrote on Mon, Oct 09, 2006 at 10:35:03PM CEST:
>
> Also, it uses "cp -p", which more-closely approximates the symlink and
> gives builders a better idea of when the source file actually changed.
If you allow me my 2c, IMVHO this approximation is a bit skewed. Under
the
Bruno Haible <[EMAIL PROTECTED]> writes:
> Would you mind adding a --copy option to the bootstrap script? Roughly
> like this?
Good suggestion, yes. I installed the following somewhat-different
patch, which is a bit more cautious about switching between a
bootstrap with and without --copy. Also
Hi Paul,
The fact that coreutils' bootstrap script creates symlinks can be an
annoyance:
- Creating self-contained tarballs requires extra effort.
- On my systems, I have a date as part of the gnulib directory name,
and rename it each time I update. In such a situation, the symlinks
br
13 matches
Mail list logo
