Hello,
On Wed, Aug 23, 2006 at 10:04:48PM +0200, Robert Schiele wrote:
> Exactly. Let's take GNOME in /opt/gnome/ as an example. If you have that you
> might want to have GNOME m4 files in /opt/gnome/share/aclocal/ but you may
> want to make some GNOME package also provide
> /usr/share/aclocal/dirlist.d/gnome that includes only the line
> "/opt/gnome/share/aclocal/".
this example is very illustrative. I think the dirlist.d/package
files would contain one absolute patch each. And that can be
expressed with an absolute symlink.
I would do
echo "/usr/share/aclocal/*.d" >>/usr/share/aclocal/dirlist
and then
ln -s /opt/gnome/share/aclocal /usr/share/aclocal/gnome.d
> Sure you could also do this with some symbolic
> links but actually in my opinion the solution I provided is more clean since
> it does not invent a new way of doing something but instead provides a
> straight-forward extension of an existing one.
My opinion is exactly oposite: why do we need to invent a new
mechanism when the current one perfectly fits the need?
Stepan
PS:
(There are some fundamental problems with the dirlist mechanism, like
when you have /opt/gnome24 and /opt/gnome26 and want to use one of
them for one build and another one for another build. But your
proposal does not help with that, so I really do not see any reason
to adopt it.)
