On Fri, 2012-06-22 at 19:37 +0200, Luk Claes wrote: > On 06/22/2012 04:31 PM, Roger Leigh wrote: > > On Fri, Jun 22, 2012 at 09:32:15PM +0800, Thomas Goirand wrote: > >> On 06/22/2012 05:34 PM, Goswin von Brederlow wrote: > >>> Step 1: upgrade/dist-upgrade with ia32-libs (wine, ...) held back > >>> Step 2: dpkg --add-architecture i386 && apt-get update > >>> Step 3: dist-upgrade (ia32-libs, wine, ... is now installable) > >>> > >> May I suggest that upon upgrade, we have a debconf message telling > >> about it? We could add this in base-files or any essential package, > >> probably one with some debconf messages already in would be a better > >> pick. Instructions would show, IF ia32-libs old version is currently > >> installed > >> AND the --add-architecture i386 hasn't bee done. > >> > >> I know we have release notes, but some don't know about them or would > >> simply not read them. A debconf message seem really appropriate IMO. > > > > Could we not introduce the concept of an "upgrade script" into > > apt-get which could be downloaded when you run "apt-get update" and > > then run during a dist-upgrade? This could handle automation of > > any "housekeeping" during the upgrade which would otherwise require > > manual work detailed in the release notes. > > Hmm, I'm not a fan of upgrade scripts at all. Either it's easy enough to > automate in maintainerscripts or it should get careful review for the > context in which it will be applied IMHO (which means the sysadmin can > run the shipped script manually). [...] You can't use a maintainer script to automate, for example, installation of another package dependent on hardware configuration. All you can do is show a note/error prompting the user to do that. Which is rather sad. Ben. -- Ben Hutchings The program is absolutely right; therefore, the computer must be wrong.
Attachment:
signature.asc
Description: This is a digitally signed message part