Bugzilla Bug 137268

As #111340 grew extremely long, and especially since the original issue of that
bug is long resolved I am opening this one to serve as a tracker of all-things
Ada related to new structure.
Please open separate bugs for the end-point reorg issues (normal bugs - e.g.
some package breaks, should not block it! They are visible for what they are
anyway). In particular, if there are any structural issues to discuss or
implement, what packages should still be ported..

Thus I am marking 111340 as a dependency.

George

Hi George.

I would like to know whether you have already decided on the issue that has
been discussed in comments #96 and #97 from bug #111340 (which this bug depends
on).

Besides what is there discussed I would like you, please, to pay attention to
another fact that has happened to me and that it speaks in favour to the
adoption of the "keep the present profile active" (gcc-like behaviour).

Before you provided the newest gnat-gpl-3.4.6 I had installed both
gnat-gpl-3.4.5 and gnat-gcc-4.1 and set this latest compiler as the active one.
My only reason behind installing gnat-gpl releases is just to check if they
work and eventually reporting bugs, while I normally use the latest gnat-gcc
for learning and production.

Some weeks ago an unattended "emerge -vu world" installed the newest
gnat-gpl-3.4.6 and set the active compiler to be that one. I forgot I still had
the old gnat-gpl-3.4.5 in the production machine where I usually delete it
after checking it succeeding in compiling a bunch of Ada libraries. 

The result is that I have been working with gnat-gpl-3.4.6 instead of
gnat-gcc-4.1 for weeks until yesterday when I discovered that. Fortunatelly I
also found out that the simple code I had sent to an italian magazine, that is
publishing an article of mine on the Ada language with some illustrative
programs, is able to compile with gnat-gcc-4.1 too as I had reported in the
same article.

fabio

Hm, looks like I did not respond here, while I seem to remember that I did.
Probably that was to that other bug. Actually yes, see comment #114 in bug
#111340 :). Anyway - the issue is resolved now.

George