Please read this before reporting a bug:
https://wiki.archlinux.org/title/Bug_reporting_guidelines
Do NOT report bugs when a package is just outdated, or it is in the AUR. Use the 'flag out of date' link on the package page, or the Mailing List.
REPEAT: Do NOT report bugs for outdated packages!
https://wiki.archlinux.org/title/Bug_reporting_guidelines
Do NOT report bugs when a package is just outdated, or it is in the AUR. Use the 'flag out of date' link on the package page, or the Mailing List.
REPEAT: Do NOT report bugs for outdated packages!
FS#10013 - awesome changes rapidly
Attached to Project:
Community Packages
Opened by Midare Kiyura (kiyura) - Saturday, 29 March 2008, 20:26 GMT
Last edited by Ronald van Haren (pressh) - Monday, 31 March 2008, 14:26 GMT
Opened by Midare Kiyura (kiyura) - Saturday, 29 March 2008, 20:26 GMT
Last edited by Ronald van Haren (pressh) - Monday, 31 March 2008, 14:26 GMT
|
DetailsDescription:
The 'awesome' window manager is purportedly stable, but between version levels as low as from 2.1 to 2.2 it will change enough that old configuration files will no longer work, and will cause awesome to fall back on the default config. For instance, the most recent upgrade to 2.2 made a good deal of the options obsolete, enough that almost everyone with a previous awesome configuration will have to make an effort to update their files. I believe this merits a post-upgrade message warning the user that their configs have, more likely than not, been outdated. Concrete examples include, but are not limited to the .awesomerc options focus_move_pointer, allow_lower_floats, align, and focustitle. This covers the range of general options, widget options, and even a widget type. Awesome's error handling is such that it will not accept even one invalid option, or it simply gives up. |
This task depends upon
Closed by Ronald van Haren (pressh)
Monday, 31 March 2008, 14:26 GMT
Reason for closing: Implemented
Additional comments about closing: implemented in awesome 2.2-3
Monday, 31 March 2008, 14:26 GMT
Reason for closing: Implemented
Additional comments about closing: implemented in awesome 2.2-3
Comment by Ronald van Haren (pressh) -
Saturday, 29 March 2008, 20:36 GMT
Do you think this type of major config changing will also occur in the future? Are these config file changes announced on the homepage, I cannot seem to find it?
Comment by Midare Kiyura (kiyura) -
Sunday, 30 March 2008, 00:20 GMT
I can't say with any certainty, but I had a conversation on their IRC channel and gathered that they make changes like this often. I don't think it would be necessary to put a post-install on every future release of awesome, but I think it should at least be put on 2.2, as it seems that many more changes than usual were made.
Comment by Ronald van Haren (pressh) -
Sunday, 30 March 2008, 19:36 GMT
Okay I will add a post-install message shortly.