Maintainer voiced his opinion, that's IMHO clear: this will not get fixed by a
_very_ (and hard to maintain) invasive distribution-specific patch in Debian nor
Ubuntu. Unless someone comes with a patch and some guarantees to maintain the
patch on the long term, it will just not happen by painting that issue as
ridiculous.
> *If* we move to a non-editable format in the future (likely for CUPS 2.0) we
> will definitely restructure things to put those files in /var/lib.
>
> I don't advise that you try to patch current CUPS to use /var/lib/cupsd for
> cupsd stuff and /etc/cups for everything else since the current code assumes
> that all CUPS configuration files are in one location. The patch will be
> very very messy and hard to maintain.
Cheers, OdyX, with his Debian Printing Team (including some cups fiddling) hat on
Maintainer voiced his opinion, that's IMHO clear: this will not get fixed by a specific patch in Debian nor
_very_ (and hard to maintain) invasive distribution-
Ubuntu. Unless someone comes with a patch and some guarantees to maintain the
patch on the long term, it will just not happen by painting that issue as
ridiculous.
That said, there's still some hope for a future solution, see bugs.debian. org/cgi- bin/bugreport. cgi?bug= 692791# 101 from Michael Sweet,
http://
upstream author:
> *If* we move to a non-editable format in the future (likely for CUPS 2.0) we
> will definitely restructure things to put those files in /var/lib.
>
> I don't advise that you try to patch current CUPS to use /var/lib/cupsd for
> cupsd stuff and /etc/cups for everything else since the current code assumes
> that all CUPS configuration files are in one location. The patch will be
> very very messy and hard to maintain.
Cheers, OdyX, with his Debian Printing Team (including some cups fiddling) hat on