Hideki Yamane writes: > On Thu, 14 Jun 2018 10:15:51 -0700 > Tianon Gravi <tia...@debian.org> wrote: >> > Instead of stretch simply defaulting to non-merged-usr, it's now >> > _blacklisted_ from merged-usr, even if I explicitly specify >> > "--merged-usr", right? Is that the intended implementation here? > > Yes, since releases until stretch was already shipped without merged-usr, > so it should be. But loose restriction for test purpose is okay, IMO. > > Question with 'EXTRACT_DEB_TAR_OPTIONS="$EXTRACT_DEB_TAR_OPTIONS -k"' > It was introduced https://bugs.debian.org/838388 , so it should not be > applied to all releases. However, I'm not sure which "older" release > for it, especially whether it equals to merged-usr.
The `-k` option doesn't work for older releases (some packages do replace files there). It should always be used for newer releases (>= stretch) to have less differences between --merged-usr and --no-merged-usr. (As it should always be applied it shouldn't be set in `setup_merged_usr` as that is misleading.) Ansgar
