[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

[Bug-dejagnu] DejaGNU 1.6-git unsetenv patch problems for GCC, Python, o

From: David Edelsohn
Subject: [Bug-dejagnu] DejaGNU 1.6-git unsetenv patch problems for GCC, Python, others
Date: Mon, 28 Aug 2017 19:38:22 -0400

In April 2016, support for "unsetenv" was removed from DejaGNU

author   Ben Elliston <address@hidden> 2016-04-24 20:46:53 +1000
committer Ben Elliston <address@hidden> 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

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

reply via email to

[Prev in Thread] Current Thread [Next in Thread]