Bug 567474

Summary:	[Future EAPI] Default to "unset DISPLAY"
Product:	Gentoo Hosted Projects	Reporter:	Pacho Ramos <pacho>
Component:	PMS/EAPI	Assignee:	PMS/EAPI <pms>
Status:	RESOLVED DUPLICATE
Severity:	normal	CC:	esigra, mgorny, tsmksubc
Priority:	Normal
Version:	unspecified
Hardware:	All
OS:	Linux
See Also:	https://bugs.gentoo.org/show_bug.cgi?id=534312
Whiteboard:
Package list:		Runtime testing required:	---
Bug Depends on:
Bug Blocks:	174380

Description Pacho Ramos gentoo-dev

2015-12-03 16:00:28 UTC

Currently we can see in the tree plenty of ebuilds needing to run "unset DISPLAY" manually to fix many different of issues (you can a few of them while grepping in the tree as comments in relevant ebuilds). Also, it's not the first time I see a test suite behaving differently depending on it finding a random DISPLAY and, then, for example, you seeing a window popping up suddenly while failing when running in console.

Is there any reason for keeping DISPLAY set to a random value while building stuff? From my point of view, we should ensure packages are built without DISPLAY and, if an ebuild need a display, it should rely on virtualx.eclass to get the X stuff handled on a predictable way

Thanks a lot

Comment 1 Ulrich Müller gentoo-dev

2015-12-04 06:59:17 UTC

This would most likely go into section 11.1 "Defined Variables".

Comment 2 Michał Górny archtester

2017-09-08 18:13:49 UTC

I don't mind this but then, I don't feel like adding more special variables is a good way forward. Maybe we should focus on the whitelist/blacklist option suggested elsewhere and WONTFIX/DUPE this one instead?

Comment 3 Ulrich Müller gentoo-dev

2017-09-09 11:01:21 UTC

Indeed, this looks like a special case that the more general blacklist would handle.

*** This bug has been marked as a duplicate of bug 499288 ***