U++ framework: Coffee corner » orphaned GCC.bm and differing source tree after upgrade

Home » Community » Coffee corner » orphaned GCC.bm and differing source tree after upgrade

Show: Today's Messages :: Polls :: Message Navigator
E-mail to friend

Re: orphaned GCC.bm and differing source tree after upgrade [message #8738 is a reply to message #8736]

Wed, 28 March 2007 17:48

mirek
Messages: 14291
Registered: November 2005

Ultimate Member

ebojd wrote on Wed, 28 March 2007 11:38

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 --

I must admit that I have not yet realized what is the right solution to this problem. The problem is that in U++, the line between "library" and "my sources" is very thin.

Putting "final" U++ sources to /usr/share/upp is just the least wrong solution:)

Mirek

Report message to a moderator

[Message index]

		orphaned GCC.bm and differing source tree after upgrade By: ebojd on Wed, 28 March 2007 17:38
		Re: orphaned GCC.bm and differing source tree after upgrade By: mirek on Wed, 28 March 2007 17:48

Previous Topic:	linux-pendrive and Upp
Next Topic:	Computer crashed

Goto Forum:

-=] Back to Top [=-

[ Syndicate this forum (XML) ] [

] [

]

Current Time: Fri Jun 19 03:19:22 GMT+2 2026

Total time taken to generate the page: 0.00708 seconds