From: Kurt H Maier <khm@sciops.net>
To: Fans of the OS Plan 9 from Bell Labs <9fans@9fans.net>
Subject: Re: [9fans] Problem with mk
Date: Wed, 18 Dec 2013 17:47:59 +0000 [thread overview]
Message-ID: <20131218174759.Horde.O-XpMbW6LWq-67M56RojQA2@ssl.eumx.net> (raw)
In-Reply-To: <CABwHSOsJ9MrBTgG5dUKw42yvfRgJZ8EyuSwGQ7capg8deRydRg@mail.gmail.com>
Quoting Blake McBride <blake@mcbride.name>:
> I'd be a better judge if I understood the purposeful, thought out reason
> behind the problems I am experiencing - assuming there is one. "That's
> just the way it works" or "we do it differently because we are not unix"
> are stupid as hell arguments.
No they aren't.
Meanwhile, I trust you have read "Maintaining Files on Plan 9 with Mk" [1]
and "Plan 9 Mkfiles" [2] in their entirety. Whining about software not
meeting your behavioral expectations will get you nowhere. Just because
other build systems make it relatively easy for you to shove unintended
functionality into tools is no reason to disparage software that is working
as intended.
khm
[1] http://doc.cat-v.org/plan_9/4th_edition/papers/mk
[2] http://doc.cat-v.org/plan_9/4th_edition/papers/mkfiles
next prev parent reply other threads:[~2013-12-18 17:47 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-12-18 15:23 Blake McBride
2013-12-18 15:37 ` dexen deVries
2013-12-18 16:07 ` Blake McBride
2013-12-18 20:21 ` Blake McBride
2013-12-18 21:04 ` Jacob Todd
2013-12-18 21:14 ` Blake McBride
2013-12-19 8:16 ` dexen deVries
2013-12-19 16:20 ` Blake McBride
2013-12-18 16:11 ` Blake McBride
2013-12-18 16:40 ` Bakul Shah
2013-12-18 17:06 ` Aram Hăvărneanu
2013-12-18 17:18 ` Blake McBride
2013-12-18 17:27 ` Rubén Berenguel
2013-12-18 17:28 ` Blake McBride
2013-12-18 17:47 ` Kurt H Maier [this message]
2013-12-18 18:13 ` Bakul Shah
2013-12-18 18:20 ` Blake McBride
2013-12-18 18:28 ` Blake McBride
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20131218174759.Horde.O-XpMbW6LWq-67M56RojQA2@ssl.eumx.net \
--to=khm@sciops.net \
--cc=9fans@9fans.net \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).