Re: A better autogen.sh

[Jim Meyering]

Eli Zaretskii wrote:

>> From: Jim Meyering <address@hidden>
>> Cc: address@hidden,  address@hidden
>> Date: Wed, 30 Mar 2011 14:03:54 +0200
>>
>> Eli Zaretskii wrote:
>> >> From: Jim Meyering <address@hidden>
>> >> Date: Wed, 30 Mar 2011 08:15:53 +0200
>> >> Cc: address@hidden
>> >>
>> >> As far as I know, bzr does not have a way to deposit a
>> >> non-version-controlled file in a just checked-out directory.
>> >
>> > What do you mean by that?
>>
>> I see no ambiguity.
>> Please rephrase the question to explain
>> precisely what you don't understand.
>
> Sorry.  Let me see if I understand you: did you mean that whenever the
> tree is updated from upstream, a file that does not exist in the
> repository should be created in the working tree?

In context you elided I mentioned a Makefile.
The request was to provide something like GNUmakefile that would
take effect also for non-GNU-make before anything like autogen.sh
or ./configure is run.  I mentioned that we don't VC Makefile.
Hence, the requestor would have to have some way of making a
bzr clone command create a non-VC'd Makefile in the directory
it creates.  AFAIK, that's not possible.