20 Mar
2012
20 Mar
'12
4:15 a.m.
On Mar 19, 2012 10:15 PM, "Darrell Anderson" <humanreadable(a)yahoo.com wrote:
use
libtools is to use the libtool.m4 and ltmain.sh installed on the system
to regenerate the files and not the files provided in each module's
sources. Therefore we don't really use libtools from any upstream sources.
Are you doing that?
Because some distros (like Ubuntu ) are woefully out of date, doesn't mean
everyone is. Trinity needs to work across the board. If its breaking in
Arch, it most likely will break Ubuntu debian or slack later
Sorry for the rant,
Calvin
I guess the question is "does the libtool
in tde need
to be updated?" ..or.. is there some way to just to bypass
the version inconsistency? It might be arch that is
having issues today, but it will be the remainder of the
distros that have the issue after a libtool update. I have
tried several times to get familiar with cmake conversion,
but as of today, I don't have the tools to tackle something
like tdeutils. I don't know if that would provide a better
solution than trying to fix libtool or how much work that
would be.
What are the thoughts of the experts?
First thought is I am not an expert!
Second thought is according to the instructions at the wiki, the way to
Third thought is although I appreciate your frustrations, seems to me the
immediate
focus for R14 should be the bug tracker and not bleeding edge I
want-my-system-to-crash every-other-day distros.
Arch Linux uses the latest versions provided by upstream projects. It is
not generally bleeding or breaking, just current. Often current versions
include bug and security fixes. I don't like people who bash Arch :)
Perhaps roll back your system to a previous version and likely most or all
of these problems disappear? Yes, we still need to address the problems ---
down the road after R14, but bleeding edge rolling distros should not be
dictating project focus. We can't keep pace now let alone with bleeding
edge.