Hello, quite interesting... today I compiled t2 for the target x86_64 (same as my host) and t2 replaced my system's libneon with its own copy.
I noticed that because suddenly my 'svn' client is no longer capable doing SSL. I had a look at the timestamp of /usr/lib64/libneon* and it was obvious. Although the concept of 'chroot' to build packages is nice, it comes always with the high risk that some configuration is done wrong and the chroot jail fails. When I build with buildroot, I don't have to be root to create my targets. That's much better from a security point of view. Well if the jail works properly, then it's ok. But this example here showed that the jail mechanism can fail. I am now a bit concerned. I would have to move my t2 dev environment to a dedicated dev server (either physical or virtual). I can only advise to everybody to do the same... regards, Ingmar ----------------------------------------------------------- If you wish to unsubscribe from this mailing, send mail to [email protected] with a subject of: unsubscribe t2
