I appreciate that it is preferable that configure does not alter the files under version control, but the consequence is that using ./configure --prefix to install byobu to an arbitrary location now creates an install which does not work out of the box; instead I must set BYOBU_PREFIX to be the installed location in my shell. This is a pain and somewhat of a surprise considering the previous behaviour of the install process.
It is entirely reasonable to expect some changes to arise in the shell scripts if you install it to a non-standard location, so minimising the diff against upstream (and comparing diffs is surely a rare activity relative to running byobu) is not a great concern.
In my view this fix introduces a bug.
I appreciate that it is preferable that configure does not alter the files under version control, but the consequence is that using ./configure --prefix to install byobu to an arbitrary location now creates an install which does not work out of the box; instead I must set BYOBU_PREFIX to be the installed location in my shell. This is a pain and somewhat of a surprise considering the previous behaviour of the install process.
It is entirely reasonable to expect some changes to arise in the shell scripts if you install it to a non-standard location, so minimising the diff against upstream (and comparing diffs is surely a rare activity relative to running byobu) is not a great concern.