diff options
| author | Michael Kerrisk <mtk.manpages@gmail.com> | 2021-05-11 04:31:46 +1200 |
|---|---|---|
| committer | Michael Kerrisk <mtk.manpages@gmail.com> | 2021-05-11 04:34:03 +1200 |
| commit | e43e45b47790bf597f62b0032d90ec0740e21c6d (patch) | |
| tree | 52ea10ff38464ec0d20cd4566158a3990021be2c | |
| parent | 80a45bed73b656ebc71f639a1528eb8386c552b1 (diff) | |
| download | man-pages-e43e45b47790bf597f62b0032d90ec0740e21c6d.tar.gz | |
Makefile: Remove shebang line
On 5/10/21 7:13 PM, Alejandro Colomar (man-pages) wrote:
> Hi Michael,
>
> On 5/10/21 1:39 AM, Michael Kerrisk (man-pages) wrote:
>>> - Specify shebang
>>
>> Why? It's not quite obvious to me, and the commit message
>> should really explain...
>
> Hmmm. I have some minor reasons to add it, but not a really good one.
>
> * Some editors don't recognize 'Makefile' as a special name, so the
> shebang helps detecting which language the file is using (e.g., for
> coloring).
>
> * I tend to subdivide a big Makefile into a small Makefile and many
> submakefiles stored in <./libexec/>. Those obviously need different
> names, and given that the makefile extension is not very standard (I use
> .mk), having a shebang helps knowing what the file is. After that, I
> also have it on the main Makefile for consistency. But here we only
> have one Makefile, so it doesn apply very much.
I think I'll remove it. It is kind of idiosyncratic, leaves the
reader asking "why?".
Signed-off-by: Michael Kerrisk <mtk.manpages@gmail.com>
| -rw-r--r-- | Makefile | 2 |
1 files changed, 0 insertions, 2 deletions
@@ -1,5 +1,3 @@ -#!/usr/bin/make -f - # Do not print "Entering directory ..." MAKEFLAGS += --no-print-directory |