cvs commit: src/usr.bin/tar Makefile

[Eric Anholt]

On Tue, 2005-04-19 at 19:48 +0300, Giorgos Keramidas wrote:
> On 2005-04-19 08:26, Eric Anholt <eta at lclark.edu> wrote:
> >On Tue, 2005-04-19 at 10:33 +0200, Dag-Erling Sm?rgrav wrote:
> >>Kris Kennaway <kris at obsecurity.org> writes:
> >>> gnu-auto* are for non-ports usage (only) - they don't mangle the
> >>> installed filenames to allow coexistence of multiple versions.
> >>
> >> It's slightly backwards, though.  What we should do is have
> >> devel/auto* for non-ports usage, installed in /usr/local/bin, and
> >> devel/ports-auto* for ports usage, installed out of the way.
> >
> > Yes!
> >
> > Working on 3rd party autotooled software outside of ports regularly is
> > miserable on FreeBSD.
> 
> I usually get around this by installing a local version of the autotools
> in /opt/autotools and adding /opt/autotools/{,s}bin before /usr/local in
> my PATH.
> 
> This has worked remarkably well for more than a year now, for software
> that has to run on FreeBSD, Linux and Solaris.

That's basically what you do with these ports
(with /usr/local/gnu-autotools/bin), but among other complaints, aclocal
stuff installed by ports doesn't get picked up by them.  So, I was
fighting for quite a while with a mysterious configure script error in
multiple packages, which it turned out was a lack of appropriate
pkgconfig aclocal bits that was being reported as an error at the wrong
line number in configure.lineno.

It sure would have been nice to be able to write code for FreeBSD during
that time, rather than fighting our broken autotools installations.

-- 
Eric Anholt                                     eta at lclark.edu
http://people.freebsd.org/~anholt/              anholt at FreeBSD.org