Hi,
Michal Čihař wrote (14 Nov 2012 07:53:12 GMT) :
> Okay, it looks like I need to use same (ugly) hack as xdebug is
> using, will do another upload.
I just tried the same upgrade path again (s,-3,-4,), and as a result
my modification change is still in xcache.ini, the (correct) absolute
extension path is in there too.
There's no .dpkg-* files around. I guess at least if there was new
default settings brought by the new conffile, .dpkg-dist should be
here, but I've no idea if it is the case. Is it?
About the extension path: after testing, I first thought "oh this is
still broken", because "Do not include full path to extension in
xcache.so." in the 2.0.0-3 debian/changelog made me think the desired
state was to *not* have the path at all in the ini file, so I thought
that would be done in the new postinst thing. But it looks like it
works fine in practice! I am confident you have tested the stable ->
2.0.0-4 upgrade path, so that one should be good too. So far, so good.
The whole thing is still unclear and prone to misunderstanding,
when reading debian/changelog. How about:
* Either the ugly postinst hack *removes* the absolute extension
path from the ini file, and the ini file does not include it to
start with -- if this is supported, which is suggested by -3 -- is
it? If this is possible, it would avoid having to deal with that
for Jessie again...
* Or a new debian/changelog entry should clarify that eventually,
we're back to including the full path.
What do you think?
Cheers,
--
intrigeri
| GnuPG key @ https://gaffer.ptitcanardnoir.org/intrigeri/intrigeri.asc
| OTR fingerprint @ https://gaffer.ptitcanardnoir.org/intrigeri/otr.asc
--
To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
