Home » Community » Coffee corner » orphaned GCC.bm and differing source tree after upgrade
orphaned GCC.bm and differing source tree after upgrade [message #8736] |
Wed, 28 March 2007 17:38 |
ebojd
Messages: 225 Registered: January 2007 Location: USA
|
Experienced Member |
|
|
I've bumped my head on an issue that we might want to discuss for later enhancements -- how to deal with differences between /usr/share/upp/*source_files* and the copy that was made to ~/upp/.
One of the problems I had came about by upgrading U++ and ended up having different versions of U++ sources from what TheIDE and my programs used for compiling the basic libraries and packages. Since I have a copy of the upp sources in ~/upp/, it uses them, but these common files do not appear to be updated when I upgrade upp.
I can envision scenarios where this is a very good thing, but in others it could cause problems.
Am I missing something, or was this intended behavior?
EBo --
|
|
|
|
Goto Forum:
Current Time: Fri Sep 20 03:20:02 CEST 2024
Total time taken to generate the page: 0.03197 seconds
|