2013/1/9 Marc Espie <es...@nerim.net>: > One important thing: as long as we're dealing with the import of > x11/kde4/ directory, it doesn't really matter if things are not > in their final form yet, as long as they get cleaned up before > they are linked to the build. > > As long as kde4 and kde3 conflict, there's no way to link both > to the build, so until kde4 works "perfectly" it won't happen.
They conflict "correctly", i.e., they could not be installed at the same time, but kdelibs-3.x could be built with KDE 4 being installed, and vice versa. > And I'm rather sure there are architectures where compiling kde4 > is currently a no-no, anything that builds qt3 and not qt4, for > instance, so like I said, having kde4 alongside kde3 might be important. Yes, of course. > But that doesn't mean you can't import things and work in-tree. > You're more likely to see progress once kde4 is committed to the > main OpenBSD tree. > > So: > - import pieces in more or less working order > - make darn sure the pieces that are already linked to the build > STAY usable for kde3 as they progress along kde4 lines. This already tested in WIP, but I can't guarantee there isn't something hidden. > (and we'll try to work out what to do wrt kde3/kde4). > > If I look at how much time I have to do stuff, I'm ways more likely > to help with kde4 is all the pieces are in the official tree rather > than in wip-openbsd... Understood. -- WBR, Vadim Zhukov
