> - Do we want to have an extensible aclocal search path? => Then a patch
> that applies to CVS HEAD must be sent upstream. If and after it has been

If someone sends this patch there now, this is easy. Otherwise I will send in
about 10 days when I am back at home again and have the time to read all the
mailing lists. If someone else sends it, I will be reachable by mail, just
don't want to send something to mailing lists I currently don't read.

> accepted, SuSEconfig.automake becomes obsolete and can be dropped.

It can be used even when the upstream integration process has not been
completed because it is in my opinion a much better solution than the current
script, even when the patch is not yet in upstream code.

> - Don't we need an extensible aclocal search path? => Then
> SuSEconfig.automake can be dropped by including a static configuration
> file which at least temporarily references /opt/gnome/share/aclocal, or
> it has to be kept, or it has to be emulated within the %post scriptlet
> of gnome-filesystem.

Sure we need an extension mechanism for that. What do you think was the
reason for implementing this dirlist stuff in aclocal at all? Even when GNOME
didn't exist the option could be used by any package that provides something
in an unusual path.

> Sorry, I have to ask again because it's still not clear to me: Are the
> current dirlist.d and the fact that everyone can use this SUSE-only
> thingy a desired feature or are they an undesired side-effect of having
> GNOME in /opt/gnome?

In my opinion it is a desired feature. It should be made a non-SUSE-only
feature but as long as mainstream does not have it it does not really hurt
because we had it anyway up to now by the script and nobody is forced to use
it.