Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Feature: Encourage stricter filename conventions #91

Open
mcandre opened this issue Mar 21, 2023 · 2 comments
Open

Feature: Encourage stricter filename conventions #91

mcandre opened this issue Mar 21, 2023 · 2 comments

Comments

@mcandre
Copy link

mcandre commented Mar 21, 2023

In order to more quickly distinguish between bmake and gmake files, we could create a new linter rule that warns on ambiguous files.

Basically, Makefile is ambiguous. This can lead to both text editors and humans assuming the wrong syntax. Any Makefile's can be disambiguated by adopting the fully lowercase makefile (bmake) or else GNUmakefile (gmake).

@mcandre
Copy link
Author

mcandre commented Mar 21, 2023

On second thought, there is value in encouraging the POSIX Makefile name. Projects that do not depend on extensions to the POSIX make standard, should follow the Makefile name.

A rule to the effect of checkbashisms would be helpful. When GNU-isms or BSD-isms are present, recommend the relevant filename. Otherwise, recommend the generic Makefile.

@cooljeanius
Copy link

One thing to consider here is how some build systems will automatically generate Makefiles with the Makefile name regardless of what sort of syntax they contain. It isn't really as easy to rename the files in such cases.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants