Re: fvwm and post.hook problem
- To: debian-user@lists.debian.org
- Subject: Re: fvwm and post.hook problem
- From: Stefan Bellon <sbellon@sbellon.de>
- Date: Fri, 09 Apr 2004 18:32:35 +0200
- Message-id: <[🔎] 4c9d02b7c5sbellon@sbellon.de>
- References: <1IZyT-4fQ-17@gated-at.bofh.it> <1IZyT-4fQ-19@gated-at.bofh.it> <1IZyT-4fQ-21@gated-at.bofh.it> <1IZyT-4fQ-23@gated-at.bofh.it> <1IZyT-4fQ-15@gated-at.bofh.it> <1J3sJ-7LM-9@gated-at.bofh.it>
hugo vanwoerkom wrote:
> Stefan Bellon wrote:
> > I don't see how the upstream FVWM mailing lists could help me with a
> > problem of the packaging of the latest Debian FVWM package.
> You know for sure that it is packaging problem and not an upstream
> change?
Yes, of course. It's just the way the configuration files are laid out
and where they are placed. There's no problem with fvwm itself.
> What does the changelog say?
* There are new utilities to help customize fvwm if there is no fvwmrc
file available. Because of this, the package removes the default
system-wide fvwmrc file, since that shadowed the nice configuration
utilities.
* The Debian menu is available from the file /etc/X11/fvwm/DebianMenu
(the old file /etc/X11/fvwm/menudefs.hook shall be retained as a
synlink for a bit). This would require a change in existing user
configuration files.
* In the postinst we now move old conffiles out of the way (.dpkg-old),
since they interfere with the new configuration generation tools; but
we do not delete the files, so preserving user changes. We only do
this if the user is upgrading from a pre 2.5.8 version. On purge, we
remove all these preserved files as well.
--
Stefan Bellon
Reply to: