Hi, I've copied NCURSES/5.6/Solaris/libtool2 to SPECS/Tools/libtool2. In this place should be a *universal* libtool2 (version 2.2.4) script. We have there libtool (version 1.5.24). Libtool2 needs *same* modifications as we have in libtool(1) done. From my point of view this is all what we need from libtool 2.2.4 .
In over 90% Dude stuff we are using just libtool script from SPECS/Tools/libtool which is copied by help Respect.pl tool into particular place (directory). AFAIK, we wouldn't use libtool from /opt/kdebld/bin/libtool, because we have lots of hacks done directly in SPECS/Tools/libtool. If we need for something libtool version 2.2.4, then we should go through same way as we did with libtool (1). I did the first step a few minutes ago (create libtool2 in SPECS/Tools). We can have both version there together. In Respect.pl we can make simple decision logic to switching between libtool's versions. Default should be libtool(1) and if some stuff needs libtool2, then we can have simple %define libtool2 yes in each particular pspc file. In futere we can swith to libtool2 is default. Libtool is hell and hacking in KBE/libtool.spec (create patches and so on) is waste of time (from my POV). We can have our hacked libtool's versions and we are independent from environments like KBE,CBE or something else. We don't need take a care about system's libtool, because we have our own. Those are the reasons why I ignore KBE/libtool.spec, every changes for libtool is done directly in SPECS/Tools/libtool script. -- Lukas 'Luc' Oboril IRC nickname: luc^ at freenode When dealing with people, let us remember we are not dealing with creatures of logic. We are dealing with creatures of emotions, creatures bristling with prejudices and motivated by pride and vanity. Dale Carnegie
