Scripsit sean finney [EMAIL PROTECTED]
i think it's kind of pointless to ask such a question at install time.
because Debian Is Not A Registry(tm)
And supposedly debconf isn't one either :-)
you have no guarantee that the debconf responses won't be nuked off
before the package is removed
Henning Makholm wrote:
It is at least conceivable for the postinst to actively store the
reply in an appropriate file in /etc which the postrm later reads.
Not that I think this would make much sense UI-wise anyhow.
Please, please don't do this! Consider what happens when the user
installs
Anthony DeRobertis [EMAIL PROTECTED] writes:
BTW: Do you really even need to ask? Couldn't you just tell the admin,
if you want to delete your data, run dropdb foo? There is a small, but
certainly nonzero, risk of accidental deletion every time you ask. I
imagine that risk increases if, e.g.,
On Sun, Aug 07, 2005 at 02:35:59PM -0700, Russ Allbery wrote:
When one does that, people file bugs complaining that the package doesn't
remove all of the data it generates on installation. :)
there's a similar problem with logfiles too, and there have been quite
drawn out discussions in which
Russ Allbery wrote:
As co-maintainer of one of the affected packages, I'm quite happy to go
along with the general consensus, since I don't really care. There seemed
to be a dislike of debconf questions in prerm and there was some precedent
for asking this sort of question in postinst, so
Russ Allbery wrote:
When one does that, people file bugs complaining that the package doesn't
remove all of the data it generates on installation. :)
[...] It's not a great solution, and I'm happy to change
if someone else has a better idea.
Well, I think the real answer is that just like
Dear Debian fellows,
what's the common practise if a package gets purged and depends on
user-supplied data in a database? In this case these are DNS zones (it's
about `mydns-mysql'). Currently there is a Debconf question in postrm,
which is definitely wrong because I cannot rely on Debconf being
Philipp Kern [EMAIL PROTECTED] wrote:
what's the common practise if a package gets purged and depends on
user-supplied data in a database? In this case these are DNS zones (it's
about `mydns-mysql'). Currently there is a Debconf question in postrm,
which is definitely wrong because I cannot
Philipp Kern [EMAIL PROTECTED] writes:
what's the common practise if a package gets purged and depends on
user-supplied data in a database? In this case these are DNS zones (it's
about `mydns-mysql'). Currently there is a Debconf question in postrm,
which is definitely wrong because I cannot
hi phillip,
On Sat, Aug 06, 2005 at 01:08:57PM +0200, Philipp Kern wrote:
what's the common practise if a package gets purged and depends on
user-supplied data in a database? In this case these are DNS zones (it's
about `mydns-mysql'). Currently there is a Debconf question in postrm,
which is
10 matches
Mail list logo
