On Wed, 15 Nov 2006 10:37:38 +0000 (GMT) Matthew Johnson <[EMAIL PROTECTED]> wrote:
> On Wed, 15 Nov 2006, Tim Dijkstra wrote: > > The postinst that I have (0.3~cvs20060928-2) does: > > # If we didn't got a value, we want the hardcoded default, > # so del > if [ -z "$VAL" ]; then SEDCMD="$SEDCMD -e '/$PATRN/ d'" > > which means that if $VAL is not set in the debconf answers that line > will be removed from the config file. But in the config script you'll see that the values from the config file are put as the default answer in the debconf database. > I am using the stock debian kernel from etch with splashy (a user-space > splash program) which is in unstable with version number 0.1.8.1-3.1 I know splashy, I'm one of the upstream authors. In the 0.3 series there will be a libsplashy which can be linked to uswsusp (created by yours truly, especially for this purpose), untill then it will not work. > However, it should either not overwrite changes (even if you don't think > there is a suitable splash system without recompiling the kernel, I > think it ought to be supported) or should be clearer in the config file > that an upgrade will overwrite and provide _all_ the questions in > debconf. It will not overwrite, I explained that it will only do that for splash, which I do agree, is a bug. Not having splash support was not the reason I designed the script to overwrite your changes. It was simply the reason I didn't discover the bug myself. Nothing more, a bug. > If it's fixed in the next upload given the rest of my comments, then > fine, but I'd like to see at least more of a warning in the config file, > and the README.Debian should _not_ say "If your not happy with it you > can choose to alter it by hand or..." That sentence will stay. Reconfiguring uswsusp (should) KEEP ALL LOCAL CHANGES. There are two separate bugs in this report that need, and can be fixed. > Sorry for hassling you on this; I'm really happy with uswsusp in > general, it works really well. The integration with splashy is also cool > (although on resume it fails to init directfb, so I don't get a splash > screen for that; that's presumably splashy's problem, not yours though) I'm confused... Dit you compile with libsplashy from svn? Else you wouldn't get any splash at all on suspend/resume... splashy is not really mature yet. It has some problems with initramfs. Also the combination initramfs and uswusp+libsplashy is not working properly yet. But that will come. grts Tim
signature.asc
Description: PGP signature
