faq
flatforty
contribute
subscribe
configure
search
rdf
main
parent
thread
|
Re: Oh no...
by Guillaume Laurent on Tuesday 13/Sep/2005, @07:19
|
Yes, pretty much all alternatives have been considered, and the only serious contenders where scons/bksys and cmake.
Second, have you ever tried to maintain an auto*-based build ? I have, and like anyone who has I can tell you how incredibly brain-damaged this system is. And it does "spill a shitload of files all over the filesystem", much more than python.
As for not wanting to install python, seriously... what's the big deal. Apparently you're resisting it for purely "religious" reasons, well, too bad. |
|
|
The Fine Print: The following comments
are owned by whomever posted them.
( Reply )
|
|
Over 40 comments listed.
Printing out index only. |
Re: Oh no...
by Me on Tuesday 13/Sep/2005, @09:20
|
No, I don't maintain any auto-* based build. This would be a nightmare, I DO agree with you on that.
As for not wanting python installed, that's not religious at all, it's just that I think that integrated solutions, neat and clean is a better way to go than "just install everything anyone could every want by default". I don't mind python or ruby or TCL or ECMAScript or whatever. People need to settle on just ONE DEFAULT ONE, integrate it the best possible in the system. But I think the situation where just everyone decide they'll use their favorite scripting language is more than suboptimal. It is OK however when the scripting language is used through a plug-in (that is choice) and you don't force those who don't need/want to use ten thousand scripting languages to install them. On the other hand I would choose TCL or Ruby over Perl and Python because these two last ones take up 50 megs of disk space.
|
[
Reply To This | View ]
|
|
|
Re: Oh no...
by ac on Tuesday 13/Sep/2005, @12:22
|
> the only serious contenders where scons/bksys and cmake.
Besides people from KDE no one else ever heard of scons or bksys.
> Second, have you ever tried to maintain an auto*-based build ?
I did and I am still doing.
> I have, and like anyone who has I can tell you how incredibly brain-damaged this system is.
There are good documents people should consider reading, if you are not willing to spent time reading the auto* documents then you are not suited to make good files that work perfectly with your software. The problem with KDE rejecting auto* is that everone I've met so far complained about auto* but in reality it's because no one really spent time reading the manuals, they all want some quick hacks so it works and they start to copy stuff from other modules and wonder why it doesn't really work. How comes millions of open source and free software except the stuff inside KDE works perfectly fine with auto* ?
> As for not wanting to install python, seriously... what's the big deal.
> Apparently you're resisting it for purely "religious" reasons, well, too bad.
That's not the point. I want to have and keep my choice of what I want to have installed on my system and not you decide what I should install. Scons will be only used in KDE and no one else in the world will probably give a damn about it except KDE. This is another step of alienation again from the KDE team of what is standard in open source. Standard still is the auto* stuff. If Scons would have been that great then by now the majority of project have switched to it and this even outside of KDE... And the reality of course looks differently.. Personally spoken for myself I do feel upset for this Scons stuff it has only been decided to be good because the author and some other two followers kept praising the hymn out of it.
|
[
Reply To This | View ]
|
|
The Fine Print: The previous
comments are owned by whomever posted them.
( Reply )
|
|
![[KDE Dot News]](http://www.kde.org/dot/Images/kdedotnews.gif)
