Opened at 2008-08-06T22:15:38Z
Closed at 2008-09-17T17:17:42Z
#499 closed defect (wontfix)
emacs thinks our makefile is a BSD makefile
| Reported by: | zooko | Owned by: | somebody |
|---|---|---|---|
| Priority: | minor | Milestone: | undecided |
| Component: | packaging | Version: | 1.2.0 |
| Keywords: | Cc: | ||
| Launchpad Bug: |
Description
The new version of emacs goes into "BSD makefile" mode when you edit our makefile, which means it might be parsing it slightly incorrectly when you use the emacs commands to navigate among rules or to create a changelog entry (? I'm just getting that from scanning the emacs lisp source code of makefile mode).
If we renamed our makefile "GNUmakefile" (again) then emacs would go into "GNUmakefile" mode instead.
However, this would bother Brian, as well as confusing some newbies whom I once watched over the shoulders of as they installed Tahoe from source.
So I would rather spend my energy on #179 (rewrite our Makefile in Python instead of GNUmake).
Change History (2)
comment:1 Changed at 2008-09-08T03:06:32Z by warner
comment:2 Changed at 2008-09-17T17:17:42Z by zooko
- Resolution set to wontfix
- Status changed from new to closed
Agreed. Closing this ticket as won't-fix.
I agree. I would be completely happy with a Makefile that was so simple that it was really just an alias for setup.py subcommands or misc/*.py utility tools, at which point there should probably not be any GNU-vs-BSD differences left in the file, and it won't matter what the name is.