Re: [patch 2/2] Implement multi-component --with-auto-load-dir

[Joel Brobecker <brobecker@adacore.com>]

> With Fedora scl-utils ("alternative packaging") you have both regular
> 	/usr/share/gdb/auto-load/
> and also the "alternative"
> 	/opt/rh/upgradeset/root/usr/share/gdb/auto-load/

I see.  I wish we could manage both with one setting.  Since we need
a "list" of directories, I'd keep "auto-load script-dir" (should we make
that script-dir plural?)...

I can see how things can be awkward for turning the safety guard off
(the equivalent of what we used to do with "auto-load safe-path").
I think I'd just make that a boolean setting instead.

> > I was hoping at some point that this would allow us to have auto-loaded
> > scripts without having to have the same path structure in the auto-load
> > directory as in the executable (by that, I mean that if you are
> > debugging /work/build/gcc-feature-a/gcc/cc1, you don't need to have
> > cc1-gdb.gdb defined in your auto-load directory as
> > auto-load/work/build/gcc-feature-a/gcc/cc1-gdb.gdb. It'd just be
> > sufficient to have cc1-gdb.gdb defined in your scripts-directory.
> > But looking at the code, I don't think that this is what we are
> > talking about.
> 
> I do not think these two features are related.  I can think about some ideas
> but I do not see a super-elegant one for it now.

No, they are not related, and you shouldn't have to worry about that
(unless you want to!). It's a feature I think some users would enjoy
having, but if I want it, I should be the one taking care of the
implementation.

-- 
Joel