Hey Lukas,
> I'm happy hear that. Idea is great, but it will not so easy to merge, as > it could be looks. > > I think that we have to have functional *spec file system* in cvsdude and > when will be everything done and smooth, then we can discuss how can we > merge it together with sfe repository. > > True is: I followed idea from sfe, when I created spec into cvsdude, but > everything isn't 1:1 copy (idea), which is be possible merge it now > Case in point: http://techbase.kde.org/index.php?title=Projects/KDE_on_Solaris#Patching_your_System QUOTE Boost, one of the dependencies, builds Python bindings, and the Python headers installed by the system Python package are broken. So you will have to edit them as root to fix this. Fortunately it will take a while before Boost gets there, so start the make process and then an editor. In /usr/include/python2.4/pyport.h there is a gethostname() prototype that must be commented out. UNQUOTE Thus we need to build Python for KDE4, again. Not sure if all the SFE/ Indiana users would want that. The Python that comes with Solaris Express/Indiana etc might be good enough for them. Also is building our own python "correct"? Correct is very subjective here. While this is certainly _required_ from KDE4/Solaris perspective, one wonders if other users would want this python to replace the other system python (And the consequences it would have for other uses/applications) Let's say package X depends on this python. Wouldnt pkgbuild-ing package X pull in python as well? Would we want that for all users? Would we want python to be pulled in only if the user asks for KDE4? Gentoo Portage has this concept of overlays. apt-get/dpkg can use multiple repositories and pull in the latest and greatest by choosing the package from all the repositories. We need something like that. We need the KDE4 .specfile repository to sit "on top of" SFE. For a non-KDE4 user/distro COMPUTER < == SFE For a KDE4 user/developer/distro COMPUTER <== KDE4 (CVSDude) <== SFE Thus the KDE repository would "wrap" SFE , override it for conflicts, not duplicate it. Does this make sense? Thanks Manish -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://mail.opensolaris.org/pipermail/kde-discuss/attachments/20080125/26b6d2e7/attachment.html>
