Hi,
> dpkg-maintscript-helper is in dpkg now, so moving or removing
> conffiles just involves pasting the same call to it into 3
> maintainer scripts.
Pasting one same call in 3 maintainer scripts is not a pain, but
it becomes a pain when you have to maintain these 3 maintainer scripts
in parallel when you delete many conffiles.
> Since to be safe it needs to know the version of the package
> in which the conffile move/removal took place, and since
> using it means a versioned predependency on dpkg, it's difficult
> to make debhelper fully automate using it.
What about postponing this for squeeze+1, which would imply a
widely-adopted dpkg, in the mandated version ?
> Still, the need to paste the same code into all the maintainer
> scripts (or most of them, and it should be ok if dpkg-maintscript-helper
> is called by all 4), is something that it seems debhelper could
> help with. Maybe have a way to insert debian/maintscript-common
> into all of them, for example.
>
> I'm not sure yet which interface makes the most sense.
I see two paths:
i) help in sharing the code between the maintscripts, with something like
dh_maintscripts. Then it is each maintainer's responsability to use the
Pre-Depends, and/or to use dpkg-maintscript-helper.
ii) Help directly the conffile handling by mandating files like
debian/$package.conffile_{rm,mv} with a specific syntax as proposed in
the
bugreport (or any else). This puts the burden of the Pre-Depends on
you, but
is the sanest way for a package maintainer like me to move and delete
conffiles in a sane way.
Both are OK, the first is probably easier and safer.
Cheers,
OdyX
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
