Will, I think your'e right.. the BSD community's goal is to have a fully BSD licensed system.. including the compiler. So, as it stands now, FreeBSD at least, uses some GPL licensed tools because there's no equivalent BSD licensed alternative. But this is happening slowly but surely. For example FreeBSD recently switched back to a BSD licensed version of tar(1), which effectively matches gnutar's features.
Within the CVS repository, GPL'd tools are separated from the rest of the system. I suspect one day we may once again return to a BSD licensed compiler as well.
Rasterman maybe just doesn't realize how important the license is to avid BSD users. So, in summary, all else being equal, a tool that's BSD licensed is certainly preferred.
3 comments:
I would like to know if the e17 TODO list is made public somewhere. Does anyone know?
It's in CVS!
Use this command (single line) to check out the code:
cvs -z3 -d :pserver:anonymous@anoncvs.enlightenment.org:/var/cvs/e checkout e17
The TODO are in e17/apps/e!
Will,
I think your'e right.. the BSD community's goal is to have a fully BSD licensed system.. including the compiler. So, as it stands now, FreeBSD at least, uses some GPL licensed tools because there's no equivalent BSD licensed alternative. But this is happening slowly but surely. For example FreeBSD recently switched back to a BSD licensed version of tar(1), which effectively matches gnutar's features.
Within the CVS repository, GPL'd tools are separated from the rest of the system. I suspect one day we may once again return to a BSD licensed compiler as well.
Rasterman maybe just doesn't realize how important the license is to avid BSD users. So, in summary, all else being equal, a tool that's BSD licensed is certainly preferred.
Great podcast as always.
Post a Comment