On Wed, Sep 10, 2014 at 04:57:56PM +1000, Stuart Prescott wrote: > Before that, I wrote : > > I'll modify pepperflashplugin-nonfree now to use the /etc/chromium.d > > approach only if /etc/chromium.d is available regardless of whether > > /etc/chromium/default exists. > > I guess pepperflashplugin-nonfree could Break versions of chromium prior to > this directory becoming available -- that would help apt help you only work > with the cooperating versions, but it might be more trouble than it's worth > too.
Creative idea, but I was rather thinking of the opposite, keeping pepperflashplugin-nonfree compatible with multiple chromium versions. So still updating /etc/chromium/default as long as an old chromium version is being used. > > Do you intend to use preinst/postinst to back out the changes that were made > to /etc/chromium/default by the older packages or is that going to be too > difficult to do? It can be done, but it's more work than I can do in short time. Also, it would only be useful if the new chromium version using /etc/chromium.d would still also have /etc/chromium/default, so possibly not useful. I await a new chromium version using /etc/chromium.d in unstable and testing for this aspect. Does this make sense to you ? Or am I overlooking something ? Regards, Bart Martens -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
