On Wed, Feb 4, 2015, at 11:14, Axel Beckert wrote: > Hi Ondřej, > > Ondřej Surý wrote: > > do you think that we can push the resolvconf compatibility to jessie? > > > > I see two possible paths here: > > > > a) add Breaks: resolvconf > > That's ok-ish. It would be the short-hack temporary solution and > likely suitable for Jessie.
okay, this is fairly easy > > b) add (Pre-)Depends: resolvconf and force resolvconf usage > > That's a no-go IMHO. (And Pre-Depends would need a discussion first on > debian-devel.) I probably don't need a Pre-Depends, but I need Depends, see below. > The common path most tools go is to check for resolvconf's existence > (IIRC /sbin/resolvconf) and decide upon that which path to go. Not > sure which dependency on resolvconf is common. I'd expect either > Suggests and/or Enhances, maybe Recommends, but it shouldn't be a hard > dependency to leave people the choice to use resolvconf or not. I have a patch that checks whether resolvconf: option has | in first place and use popen instead of fopen in such case. I will be uploading that to experimental shortly. The problem with just checking for resolvconf existence is: 1. install dnssec-trigger 2. /etc/resolv.conf becomes +i 3. install resolvconf 4. it breaks So unless there's a way how dnssec-trigger can hook into resolvconf postinst, it won't play well. Also we will need to have lo.dnssec in first place in the list of priorities and a way how to tell resolvconf to stop after localhost (e.g. trigger TRUNCATE_NAMESERVER_LIST_AFTER_LOOPBACK_ADDRESS when dnssec-trigger is installed). Cheers, -- Ondřej Surý <ond...@sury.org> Knot DNS (https://www.knot-dns.cz/) – a high-performance DNS server -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
