Re: problems with 2 automakes

[Alexandre Duret-Lutz]

>>> "Alien999999999" == Alien999999999  <address@hidden> writes:

 Alien999999999> I have a problem, i want to use the KDevelop
 Alien999999999> (which requires automake-1.4), but most of my
 Alien999999999> projects require automake >=1.6 . I do not wish
 Alien999999999> to uninstall KDevelop, which i have done
 Alien999999999> before, to enable to use the automake-1.7 and
 Alien999999999> others...

automake 1.4-p6, can perfectly coexist with automake 1.6.x,
1.7.x, or 1.8.x.  You just have to install all of them.  The
last package you install will use the names `automake/aclocal',
the other will be available as automake-1.4/aclocal-1.4,
automake-1.6/aclocal-1.6, etc.

I recommend that you keep `automake/aclocal' for the last
release, and adjust projects that need specific versions
to run the correct versioned binary.

See also `Automake API versioning' in the manual.

(BTW I'm only talking about the GNU packages.  I've seen many
RPM packages where aclocal is patched in a way that prevents any
attempt to such side-by-side installation.)

 Alien999999999> most importantly, i want that the
 Alien999999999> WANT_AUTOMAKE_1_6=1 env variable or the version
 Alien999999999> option in the configure.ac file works.

There is no such variable in the version we maintain, it must be
a change local to your distribution/environment.  (Or it doesn't
exist at all, which would explain why it doesn't work...)

[...]

-- 
Alexandre Duret-Lutz