Am 10.05.2012 23:00, schrieb Alexander Neundorf: .... > The situation with the tier1 libs is very different than with KDE4 > kdelibs: no dependencies between each other, no runtime dependencies. > > Why not put all tier1 libraries into one repository and release them as > one package ? > > Keep tier2 and tier3 libraries, or those which introduce different > runtime dependencies, or those which are "big", separate. > > qxt does this too, and it's no problem for 3rd party users. > > Having the tier1 libs in one repository would at least make maintaining > the buildsystem easier (simply less work), and it may make building the > whole thing a bit more convenient, since you have less packages to build. > > For kdelibs developers it would be probably also a bit more convenient. > > Of course each of the libs can be switched on and off separately... > > So, what are the real benefits of e.g. releasing the 6-file library > kdbusaddons as a separate package ?
There are definitely tier1 libs that are interesting completely on their own (thinking of solid e.g.). Also, I don't think a lot of people compile KDE by hand, not on Linux nor on any other platform. The main problem I see if you keep the libraries together, you will end up in a similar way as Qt5 does atm: "This project is using private headers and will therefore be tied to this specific Qt Module build version" - so the need (==advantage) to have clean library splitting will go away as soon as possible again. > > Alex > > regards, Patrick _______________________________________________ Kde-frameworks-devel mailing list Kde-frameworks-devel@kde.org https://mail.kde.org/mailman/listinfo/kde-frameworks-devel
