the applications will get frozen in a
distribution, because newer applications would need newer libraries
* or we get into branching / #IFDEF madness, because older libraries require
other codepathis in applications
Thoughts?
Cheers, Andreas
--
Dr. Andreas K. Huettel
Institute for Experimental
on follow the same workflow as the rest of kde again. With Git that is
certainly possible.
Which obviously does not mean that suddenly all of kdelibs should be rewritten
or broken. However, imposing this branch weirdness on everyone else for pure
political reasons is just wrong.
--
Andreas K
right with this point, I apologize. Reading the git log, the
changes are indeed same order of mangnitude as before.
--
Andreas K. Huettel
Gentoo Linux developer
dilfri...@gentoo.org
http://www.akhuettel.de/
signature.asc
Description: This is a digitally signed message part.
for a couple of weeks already.)
Cheers,
Andreas
--
Andreas K. Huettel
Gentoo Linux developer
dilfri...@gentoo.org
http://www.akhuettel.de/
signature.asc
Description: This is a digitally signed message part.
as a working
whole, not released as an assembly of hopefully working pieces.
--
Andreas K. Huettel
Gentoo Linux developer
dilfri...@gentoo.org
http://www.akhuettel.de/
signature.asc
Description: This is a digitally signed message part.
Visit http://mail.kde.org/mailman/listinfo/kde-devel#unsub
with the if they
like part, since we all know already how much pain the out of sync kdepim
caused. Suggestion 2 fails with the independent of the schedules part,
because you can't release somthing that is not stabilized and tested.
Please try to get some sense back...
Cheers,
Andreas
--
Andreas K. Huettel
made some very valid points there. Breaking KDE up does not help, and the
coordinated releases were/are a great thing.
--
Andreas K. Huettel
Gentoo Linux developer
dilfri...@gentoo.org
http://www.akhuettel.de/
signature.asc
Description: This is a digitally signed message part.
Visit http
