Bug 24631 imported from GNA! bug tracker
Submitted by: bkorb on 2016-05-01 21:38:38
Proper messaging is extremely important. I just tried (and failed) to configure your project. The problem with your configure script is that it immediately fails just as soon as it discovers an issue. That means I must go through a loop of attempting to configure, failing, checking why, installing the missing component and going back to step 1. It is possible to collect known missing components and print them all out at the end so I can decide if I want to fix them all or give up. In the end, I fixed issue after issue after issue and finally got to:
> Your intltool is too old. You need intltool 0.35.0 or later.
for which I don't really know what to do. My distro is very new and is very unhappy to install a later version because it conflicts with other stuff that "needs" the older one. So after an hour of futzing around, I am SOL. With better messages, I'd have known that an hour ago.
Comment by: eossoe on 2016-05-02 02:31:18
Solution:$ sudo apt-get install intltool
Comment by: bkorb on 2016-05-02 18:57:21
I guess I was insufficiently clear. Though the message "Your intltool is too old" is (somewhat) misleading in that intltool was entirely missing, that really is not the important point I was trying to make. (Probably the intltool folks need to fix that in their configure stuff, dunno.)
HERE IS THE ISSUE:
the entangle configure script has a gazillion dependencies. Because of that, the script needs to collect a list of deficiencies and print the list in a wrap-up fail-exit. This is important because it is a real nuisance to fix gazillions of deficiencies one at a time. Either that, or in the fail-exit code, refer the hapless to a current list of dependencies. That may be easier for you, but the downside is that external lists get out of date. The configure script is more likely to be kept current.