Frank Brickle <[EMAIL PROTECTED]> writes: >> Given that new versions of python can be installed and made default >> (meaning invoked as 'python'), it's necessary to bind the scripts to the >> same version of python used to build .so modules and install .py files >> in site-packages... > > I'm curious -- really just curious -- why not create a chroot > environment for gnuradio? Or, where the kernel and the CPU allow, > a fully virtualized stable OS install simply for gnuradio?
You could, but a chroot per package would lead to a vast number of chroots, and it wouldn't solve the underlying problem of maintaining dependencies. If one views the computer's sole purpose as providing a way to run Gnu Radio, that might be reasonable. If one views GNU Radio as one of many components in an overall system - for instance providing the low-level network connectivity, then it isn't reasonable. The lack of python binding really is just plain suboptimal (or wrong) - but becaues most people rarely change python bindings, and because GNU Radio hackers constantly rebuild/reinstall GNU Radio, it hardly ever causes trouble. I don't expect other people to fix this if they don't want to spend the effort. pkgsrc currently works around this by having a list of files in which the interpreter is changed as they are installed. _______________________________________________ Discuss-gnuradio mailing list Discuss-gnuradio@gnu.org http://lists.gnu.org/mailman/listinfo/discuss-gnuradio
