Re: [PATCH] Fix python compatibility with old versions of GDB

[Matt Rice <ratmice at gmail dot com>]

On Tue, Jun 13, 2017 at 10:29 AM, Simon Marchi <simon.marchi@polymtl.ca> wrote:
> On 2017-06-13 16:44, Eli Zaretskii wrote:
>>
>> FWIW, I always configure GDB to use a version-specific data-directory,
>> because I leave old GDB versions (renamed) on my system, so I could
>> still use them after installing a new version.  E.g., if the new
>> version turns out to have a bug.  I would actually be happier if we
>> changed our installation scripts to do that by default, because the
>> scripts are almost never backward-compatible IME.
>
>
> Can you give more details on what you think could/should be done by default?
>
> For such a use case, I would compile each gdb with a separate prefix (e.g.
> --prefix=/opt/gdb/<version>), which would give each install its own data
> directory.  So from my point of view, the "feature" is pretty well-covered.

Is there any argument against appending version to the data-directory
by default?

e.g. gcc configures /usr/lib/gcc/triplet/version?  I see a number of
/usr/share/*/[0-9]\.* directories here.