[kde-freebsd] libdraw-kder - no longer builds on gcck
John Marino
freebsd.contact at marino.st
Tue Jun 9 05:02:16 UTC 2015
On 6/9/2015 02:47, Sergey A. Osokin wrote:
> On Mon, Jun 08, 2015 at 11:57:34PM +0200, John Marino wrote:
>> Hi Sergey,
>> Okay, we'll the maintainer is "kde@".
>> kde4 is broken now on FreeBSD 8 and 9 (libdraw-kde4 takes out 50
>> packages) so this is pretty serious.
>
> Hi John,
>
> if it's serious, it's up to maintainer to provide a fix for the issue, this is open source world.
> I'm not using KDE4, so, I don't think I can help in this case.
I can't say I really agree with either sentiment here.
Generally if one updates a port that others depend on, there is some
responsibility for fallout. It's not really fair to hold downstream
ports accountable for others actions when they weren't even notified.
Secondly, one doesn't have to run KDE4 to "help". They only have to try
to build libdraw-kde4 (a port KDE4 depends on). Poudriere testport
would preload it's requirements and and "-i" would give a prompt after
the build.
I don't use KDE4 either but I know it's possible to trouble this problem
without it.
>
>> I think chances are pretty good that this is a direct result (fallout)
>> of updating libraw so we might be talking about a revert here.
>
> Well, I don't think that's possible to revert back last changes for libraw cause it was
> security update.
Well, sure it's possible.
It's probably not the recommended approach -- it's probably better to
make libkdraw-kde4 build with it, but I think all options are available.
I think I'd even add a comment to libraw to not update again without
confirming kde4 still builds.
In the end, basically libkdraw-kde4 (or libraw) is missing a compiler
flag. It's probably an easy fix. It's probably taking longer to write
emails than it is to fix it.
Later, I'm off to the airport now.
John
More information about the kde-freebsd
mailing list