Hi Sven, Am Sonntag, den 23.08.2015, 18:18 +0200 schrieb Sven Bartscher: > > Note that my package does _not_ touch or put files in /srv. It > > merely > > uses files that are put in a certain directory that, that the admin > > has to create first. Does that mitigate your concerns? > > A problem, that I see with this, is that someone might already > use /srv/local-apt-repository for something else. If that something is > an apt repository (which is not unlikely with the given name) you might > accidentally install files on your system, that weren't intended to be > installed. I would expect that an admin would read the description of the package before installing it, and the description quite plainly tells him that this will happen. > With a debconf question, the admin is confronted with the > fact, that this directory will be read, before doing so. > > If you don't want to do the debconf stuff, I offer to do it, as I have > to get to know maintainer scripts and debconf anyway. Thanks for the offer! If I have to do that, I’ll happily accept it. But I hope that there is a way to make this work out-of-the box, without the requirement of admin intervention and with a sensible default path. Greetings, Joachim -- Joachim "nomeata" Breitner Debian Developer nomeata@debian.org | ICQ# 74513189 | GPG-Keyid: F0FBF51F JID: nomeata@joachim-breitner.de | http://people.debian.org/~nomeata
Attachment:
signature.asc
Description: This is a digitally signed message part