In develbranch_6, is there any reason NOT to add arraystats to ../lib/Makefile, v.class to ../vector/Makefile, or d.thematic.area to ../display/Makefile?
I can do this, but want to make sure that there is not a problem in doing so.
Michael
Michael Barton wrote:
In develbranch_6, is there any reason NOT to add arraystats to ../lib/
Makefile, v.class to ../vector/Makefile, or d.thematic.area to ../
display/Makefile?I can do this, but want to make sure that there is not a problem in
doing so.
Nope. The worst that can happen is that those directories fail to
compile. It shouldn't be able to cause anything else to fail.
--
Glynn Clements <glynn@gclements.plus.com>
On 08/09/08 11:19, Glynn Clements wrote:
Michael Barton wrote:
In develbranch_6, is there any reason NOT to add arraystats to ../lib/ Makefile, v.class to ../vector/Makefile, or d.thematic.area to ../ display/Makefile?
I can do this, but want to make sure that there is not a problem in doing so.
Nope. The worst that can happen is that those directories fail to
compile. It shouldn't be able to cause anything else to fail.
Done:
33325 and 33326 (sorry, thought about grouping all files in one commit too late...)
Moritz
Thanks.
Michael
On Sep 8, 2008, at 5:13 AM, Moritz Lennert wrote:
On 08/09/08 11:19, Glynn Clements wrote:
Michael Barton wrote:
In develbranch_6, is there any reason NOT to add arraystats to ../lib/ Makefile, v.class to ../vector/Makefile, or d.thematic.area to ../ display/Makefile?
I can do this, but want to make sure that there is not a problem in doing so.
Nope. The worst that can happen is that those directories fail to
compile. It shouldn't be able to cause anything else to fail.Done:
33325 and 33326 (sorry, thought about grouping all files in one commit too late...)Moritz