diff options
| author | Eli Schwartz <eschwartz93@gmail.com> | 2023-10-02 02:55:48 -0400 |
|---|---|---|
| committer | Zac Medico <zmedico@gentoo.org> | 2023-10-17 21:37:15 -0700 |
| commit | af5d2713d365e38de261c205cfd795edc337e540 (patch) | |
| tree | 569c7740d16ed29bfa42805e754d24a870c9f256 /dev-python/python-openstackclient/python-openstackclient-6.3.0.ebuild | |
| parent | 4103983d9ac27718dad9f5cbf9ea5bdf03aeb7ac (diff) | |
| download | gentoo-af5d2713d365e38de261c205cfd795edc337e540.tar.gz gentoo-af5d2713d365e38de261c205cfd795edc337e540.tar.bz2 gentoo-af5d2713d365e38de261c205cfd795edc337e540.zip | |
app-text/calibre: Remove erroneous "binary install" workaround
This has never been caused by the upstream binary install, which
installs to /opt and does not affect from-source installs under any
circumstances ever.
What did happen is back during the major version update from 2.85 to
3.0, upstream stopped including a vendored regex/ module, and started
expecting it to be installed as a system dependency.
Under most circumstances, this was fine, and simply installing the
dependency would get things working. One possible edge case occurred,
however, when the old version of the package did NOT byte-compile the
vendored regex module, but calibre was run as root. (There are reasons
it might end up being run as root, the most obvious being that a user
wanted to run the headless server or another command-line tool.)
If this happened, then the python interpreter would automatically
byte-compile every module on import, but the PM wouldn't track it for
removal. After an upgrade, the cached file could still be imported and
would effectively mask the system version of the regex module, but would
be missing the binary portion.
Signed-off-by: Eli Schwartz <eschwartz93@gmail.com>
Signed-off-by: Zac Medico <zmedico@gentoo.org>
Diffstat (limited to 'dev-python/python-openstackclient/python-openstackclient-6.3.0.ebuild')
0 files changed, 0 insertions, 0 deletions
