Hi! Sorry for troubling you all... In my unauthoritative opinion, the problem is much more deep. CRUX has some set of ports, that other ports are very sensible to. At this time, i can talk about three ones: perl, python and openssl. Obviously, gcc and glibc are also of such kind ) Well, while jumping to a 2.2 branch of core/opt, I had a problem with openssl. Each executable, that had been using libssl.so.0.9.7 failed to start and I had to recompile the port with it. Speaking about perl/python, the patch mentioned leads to potential hard to find compatibility problems. I think it's more simple to mark such ports with in special fashion - saying 'this port is special, all dependencies have to be rebuilt'. This does not break a KISS and follows CRUX's manner of optional extensions. And it's not a big problem to recompile a dozen of ports that ARE AVAILABLE in source dir. Furthermore, the port can be marked eventually - with a minor version jump (python), or permanently (perl updates) prt-get could list such ports after update or even automatically rebuild them if requested. Not pretending this to be considered as a solution of course, but would like to hear you opinion anyway :) Originally Mark Rosenstand wrote:
The main patch is the following: http://jw.tks6.net/files/crux/major.version.cygwin.sh.patch.txt
Seems easy enough to try IMO.
-- Oleksiy