On Sat, 2022-10-22 at 21:13 +0100, Tim Murphy wrote:
> On Sat, 22 Oct 2022, 20:33 Paul Smith, wrote:
> > "Updating a target" has a well-defined meaning that's used
> > everywhere in the documentation and the mailing lists etc., and
> > it's also the term used everywhere in the POSIX spec for the
>
On Sat, 22 Oct 2022, 20:33 Paul Smith, wrote:
> On Wed, 2022-10-19 at 07:28 +0100, Tim Murphy wrote:
> > Outside of make "update" implies existence - we use CRUD as a term
> > for example not RUD. Why redefine the language? Actually for
> > databases the word "upsert" has been invented to explai
On Wed, 2022-10-19 at 07:28 +0100, Tim Murphy wrote:
> Outside of make "update" implies existence - we use CRUD as a term
> for example not RUD. Why redefine the language? Actually for
> databases the word "upsert" has been invented to explain a roughly
> analagous situation is going on - perhaps
On Sat, 15 Oct 2022 at 23:57, Paul D. Smith wrote:
> Follow-up Comment #1, bug #62936 (project make):
>
> I don't know why you say "you cannot update a non-existing file": make does
> this all the time! When you start make in a clean directory there are no
> object files, for example, and so tho
Hi Konrad,
> Trying to understand a bug in my Makefile, I consulted the manual
> section on chained rules
> (https://www.gnu.org/software/make/manual/html_node/Chained-Rules.html#Chained-Rules)
> and found the following paragraph, which is more confusing than
> helpful:
>> The first difference is
