Community Packages

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!
Tasklist

FS#11819 - awesome 3: post_install needs to be fixed

Attached to Project: Community Packages
Opened by Pierre Chapuis (catwell) - Tuesday, 21 October 2008, 06:49 GMT
Last edited by Ronald van Haren (pressh) - Thursday, 06 November 2008, 14:15 GMT
Task Type Bug Report
Category
Status Closed
Assigned To Ronald van Haren (pressh)
Architecture All
Severity Low
Priority Normal
Reported Version
Due in Version Undecided
Due Date Undecided
Percent Complete 100%
Votes 0
Private No

Details

Description:

As of now, post_install() outputs this text:

==> awesome installation notes:
----------------------------------------
During some updates of awesome, the config file syntax changes heavily.
This means that your configuration file (~/.awesomerc) for another than
this particular version of awesome may or may not work.

but the configuration file for awesome 3 is .config/awesome/rc.lua, so I think it needs to be updated to reflect this change.

By the way, I think a news stating that awesome 3 had gone to core would've been a good idea since it is a major version which breaks the user configuration completely.

Additional info:
* awesome 3.0-1.1

Steps to reproduce:

Install or upgrade awesome (since post_upgrade runs post_install).
This task depends upon

Closed by  Ronald van Haren (pressh)
Thursday, 06 November 2008, 14:15 GMT
Reason for closing:  Implemented
Additional comments about closing:  replaced ~/.awesomerc by ~/.config/awesome/rc.lua in the install file in awesome 3.0-2
Comment by Ronald van Haren (pressh) - Tuesday, 21 October 2008, 10:43 GMT
I'll fix the post-install message....why do they even change the location of the users config file :p
Comment by Thayer Williams (thayer) - Thursday, 06 November 2008, 06:44 GMT
Awesome went to core?!?! That scared the hell outta me when I read that...

AFAIK, the upgrade broke the users' preferred configuration, but not their X session entirely. I see that as non-critical and frankly, awesome is under such rapid development that its users should be aware of these changes or, at the very least prepared to deal with them.

Loading...