http://qa.mandrakesoft.com/show_bug.cgi?id=1751


[EMAIL PROTECTED] changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |[EMAIL PROTECTED]




------- Additional Comments From [EMAIL PROTECTED]  2003-25-09 10:26 -------
It is still valid. MDK 9.2 RC 2 is still 'an unfriendly place' for people
wishing to develop applications with KDE - we really need upgraded versions of
autoconf (in MDK is now 2.13; latest version is 2.57) and automake (in MDK is
now 1.4; latest version is 1.77).

In my updated 'Cooker' installation, it seems that only two packages expressly
(i.e. reported by 'rpm -q --whatrequires autoconf') depend on autoconf and
automake: kdevelop (a package that has its own serious problems, see bug #3202
and others) and rpm-build. I don't know if they are really dependent on the old
version or if it's merely a question of depenency definitions in the packaging.

It seems to me that getting KDE stuff compiled (using 'konstruct' perhaps) is
more important than even supporting (a partly broken) KDevelop 2.1.5 for the
time being . We must probably wait for KDevelop/Gideon 3 and KDE 3.2 for the IDE
stuff to be fully (?) sorted out.

-- 
Configure bugmail: http://qa.mandrakesoft.com/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are on the CC list for the bug, or are watching someone who is.


------- Reminder: -------
assigned_to: [EMAIL PROTECTED]
status: NEW
creation_date: 
description: 
Forcing an install, KDevelop seems to work fine with automake1.6, and 
autoconf2.5 
 
eg. 
> rpm -Uvh kdevelop-2.1.5-2mdk.i586.rpm 
> error: failed dependencies: 
>         automake1.6 conflicts with kdevelop-2.1.5-2mdk 
>         autoconf2.5 conflicts with kdevelop-2.1.5-2mdk 
> [EMAIL PROTECTED] RPMS]# rpm -Uvh --nodeps kdevelop-2.1.5-2mdk.i586.rpm 
> Preparing...                
########################################### [100%] 
>    1:kdevelop               
########################################### [100%]

Reply via email to