-
Notifications
You must be signed in to change notification settings - Fork 44
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
Comments
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 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 |
One thing to consider here is how some build systems will automatically generate Makefiles with the |
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. AnyMakefile
's can be disambiguated by adopting the fully lowercasemakefile
(bmake) or elseGNUmakefile
(gmake).The text was updated successfully, but these errors were encountered: