Opened 16 years ago
Closed 16 years ago
#388 closed defect (fixed)
*.tcl installed as executable
Reported by: | hamish | Owned by: | |
---|---|---|---|
Priority: | minor | Milestone: | 6.4.0 |
Component: | Installation | Version: | svn-develbranch6 |
Keywords: | build install | Cc: | |
CPU: | Unspecified | Platform: | Linux |
Description
Hi,
browsing through the Debian lintian package report for grass 6.2.3 I notice that the .tcl files installed in $(ETC)/dm/,gm/ are incorrectly given an executable bit in the file system.
http://lintian.debian.org/maintainer/pkg-grass-devel@lists.alioth.debian.org.html#grass
some Makefile magic required..
Hamish
Change History (3)
follow-up: 2 comment:1 by , 16 years ago
comment:2 by , 16 years ago
Replying to glynn:
I've changed gis.m/Makefile from $(INSTALL) to $(INSTALL_DATA) in r34721. tksys.tcl is an executable script, so I explicitly added execute permission for that file.
thanks.
d.m would need something similar, if we're going to keep it. Is there any reason to?
Apparently some people prefer it. All the g.gui and init.sh stuff is set up to handle it well in a mixed environment; it doesn't hurt anything; and has taken minimal effort to maintain. So I'd say there's no reason to remove it.
Does it still work?
yes, it works fine.
Hamish
comment:3 by , 16 years ago
Resolution: | → fixed |
---|---|
Status: | new → closed |
Replying to hamish:
I've changed gis.m/Makefile from $(INSTALL) to $(INSTALL_DATA) in r34721. tksys.tcl is an executable script, so I explicitly added execute permission for that file.
d.m would need something similar, if we're going to keep it. Is there any reason to? Does it still work?