On Wed, Feb 27, 2019 at 04:58:51PM +0100, Matthias Klose wrote:
> This has to be fixed on the dico side. One possible solution is to guard the
> import and fall back to some defaults, either provided inline, or using a
> defaults config file shipped in /usr/lib/... This way the package can be
> installed with the dangling symlink.
>
---end quoted text---
That would mean shipping the same conffile as
'/usr/share/dicoweb/settings_defaults.py' for eg.
And adding a custom Debian patch in all these files forever:
dicoweb/templatetags/media.py:from django.conf import settings
dicoweb/urls.py:from django.conf import settings
dicoweb/views.py:from django.conf import settings
with a try/except that would import from 'settings_defaults' if the
original import fails.
That also means we would need to track newer versions for such imports
to augment the patch, forever.
That is horribly ugly to say the least, and for a kind of symlink used
to move the config in /etc, which is far from being unheard of in
Debian.
Also, a user who has a custom config. would rather prefer that
dicoweb would fail to start instead of open with default config if the
symlink became dangling for some reason.
Can't there be another workaround for this ?
--
أحمد المحمودي (Ahmed El-Mahmoudy)
Digital design engineer
GPG KeyIDs: 4096R/A7EF5671 2048R/EDDDA1B7
GPG Fingerprints:
6E2E E4BB 72E2 F417 D066 6ABF 7B30 B496 A7EF 5761
8206 A196 2084 7E6D 0DF8 B176 BC19 6A94 EDDD A1B7
signature.asc
Description: PGP signature
