Klemens Nanni <[email protected]> wrote: > On Tue, Sep 18, 2018 at 03:44:27PM -0600, Theo de Raadt wrote: > > I honestly think this is a foolishly complicated. > > > > Just install the program, then run regress. Install an older version > > without the broken changes if it doesn't work. > > > > I tire of these interactions between environment variables, > > base build methods, fork+exec paths in privsep programs, and now > > getting tied into regress tests. > > > > In a word, YUCK. > > > > I think this isn't "convenience". Rather it comes off as artifically > > complicated, trying to solve a problem which doesn't need to be exist > > at all. Perhaps even perceiving there to be a problem which needs > > solving via such abstration is the true problem. > For me it clearly is convenient and actually less overhead.
So piles of chicken scratches -- just for you? > Why elevating to root and writing to /usr for each test instead of just > pointing it at my local build? A regress test's purpose is to verify that the new program passes known tests. You may as well install it, because you endeavor to make a correct program, don't you? I find it strange you are so terrified of evelating to root to install the program which later on gets run as root. But basically, I believe there must be resistance against the continual desire to abstract the regression tests further and further, to the point where fewer people understand them and fewer people run them. The desire to introduce complexity is a disease. So basically you can see I disagree with the approach being taken here for numerous reasons.
