diff options
author | David Kalnischkies <david@kalnischkies.de> | 2016-07-19 18:20:38 +0200 |
---|---|---|
committer | David Kalnischkies <david@kalnischkies.de> | 2016-07-19 18:20:38 +0200 |
commit | 475f75506db48a7fa90711fce4ed129f6a14cc9a (patch) | |
tree | ee4682166475a14a47c71b4dd6aa8a24c2c29229 /test/integration/status-bug-lp1347721-dpkg-ordering | |
parent | bbd8308cc01941e51e2cbcf88168a5560abe6042 (diff) |
don't hardcode /var/lib/dpkg/status as dir::state::status
Theoretically it should be enough to change the Dir setting and have apt
pick the dpkg/status file from that. Also, it should be consistently
effected by RootDir. Both wasn't really the case through, so a user had
to explicitly set it too (or ignore it and have or not have expected
sideeffects caused by it).
This commit tries to guess better the location of the dpkg/status file
by setting dir::state::status to a naive "../dpkg/status", just that
this setting would be interpreted as relative to the CWD and not
relative to the dir::state directory. Also, the status file isn't really
relative to the state files apt has in /var/lib/apt/ as evident if we
consider that apt/ could be a symlink to someplace else and "../dpkg"
not effected by it, so what we do here is an explicit replace on apt/
– similar to how we create directories if it ends in apt/ – with dpkg/.
As this is a change it has the potential to cause regressions in so far
as the dpkg/status file of the "host" system is no longer used if you
set a "chroot" system via the Dir setting – but that tends to be
intended and causes people to painfully figure out that they had to set
this explicitly before, so that it now works more in terms of how the
other Dir settings work (aka "as expected"). If using the host status
file is really intended it is in fact easier to set this explicitely
compared to setting the new "magic" location explicitely.
Diffstat (limited to 'test/integration/status-bug-lp1347721-dpkg-ordering')
0 files changed, 0 insertions, 0 deletions