In April 2016, support for "unsetenv" was removed from DejaGNU author Ben Elliston <b...@gnu.org> 2016-04-24 20:46:53 +1000 committer Ben Elliston <b...@gnu.org> 2016-04-24 20:46:53 +1000 commit c7185dfb66b0b278709d869ba020eec8348796ef (patch)
The unsetenv procedure is used extensively in DejaGNU testsuites for Python, GCC, libffi and other Free Software and OSS project. If a release is made from current Git and deployed in Linux distributions, testsuites for a large number of projects are going encounter numerous DejaGNU errors. Is it really in the best interest of DejaGNU to break the testsuite world with this change? Is it really useful to copy the implementation of unsetenv into each and every project that uses DejaGNU? If DejaGNU creates a release with this change, I strongly recommend labeling it DejaGNU 2.0, or at least 1.7, to make the API breakage very clear. Thanks, David _______________________________________________ Bug-dejagnu mailing list Bug-dejagnu@gnu.org https://lists.gnu.org/mailman/listinfo/bug-dejagnu
