Bug#633497: add abort method

[jidanni]

> "CP" == Christian PERRIER  writes:

CP> Ever heard about the "backup" capability?
CP> debconf-devel(7) gives good clues about it.
Of course I've never heard of it, I am an end user. Nor have I ever
encountered any configuration that offered it... reading up on it it
looks good -- it is just unfortunate that the default apparently is that
the script writer must turn all that stuff on -- vs. say a shell script
where the writer would have to intentionally use "trap" to turn
interrupts off. Yes you can close this bug if you wish.



-- 
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org

Bug#633497: add abort method

[Christian PERRIER]

Quoting jida...@jidanni.org (jida...@jidanni.org):
> Package: debconf
> Version: 1.5.40
> Severity: wishlist
> File: /usr/sbin/dpkg-reconfigure
> 
> dpkg-reconfigure is totally unreasonable in not providing any kind of
> abort key.


Ever heard about the "backup" capability?

debconf-devel(7) gives good clues about it.

What might be confusing for you is that this is up to the packages'
configure scripts to implement this, because different actions may
have to be taken when users hit Cancel or Back, depending on the
context.

I suggest closing this bug report. Then please file a gazillion of bug
reports when you meet packages that do not implement the backup
capability. Preferrably with patches.





signature.asc
Description: Digital signature

Bug#633497: add abort method

[jidanni]

Package: debconf
Version: 1.5.40
Severity: wishlist
File: /usr/sbin/dpkg-reconfigure

dpkg-reconfigure is totally unreasonable in not providing any kind of
abort key.

Just think of all the forms you have ever filled out, did even one not
provide some option to get out now?

And as you have disabled ^C, you at least should map it to a warning
message that says "quitting now might ..., are you sure?  ".

Yes, aborting in some dialogs might have different consequences than
others... still no excuse not to provide a way out.

Yes we could remotely kill the session, or unplug our computer, but
wouldn't it be better to not just leave the user to figure out a way to
stop your program?



-- 
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org