#21303 closed update (fixed)
awesome-3.3.4 update
| Reported by: | macports.org@… | Owned by: | milosh@… |
|---|---|---|---|
| Priority: | Normal | Milestone: | |
| Component: | ports | Version: | 1.8.0 |
| Keywords: | Cc: | ||
| Port: | awesome |
Description
The following Portfile diff updates the awesome window manager package to the latest release 3.3.4.
The upstream version switched to cmake. The portfile may need some rework concerning the following issues.
- XDG: Even though XDG_CONFIG_HOME is set to /opt/local/etc/xdg, the final awesome binary tries to find the config file (rc.lua) in the directories /etc/xdg/awesome and ~/.config/awesome/
Setting XDG_CONFIG_HOME=/opt/local/etc/xdg in the .xinitrc file or copying the default config file to the home config directory solves this issue
cp /opt/local/etc/xdg/awesome/rc.lua ~/.config/awesome/
- variant x11_xcb: the new awesome package needs cairo to be installed with variant +x11_xcb. I couldn't manage port to install/upgrade it with the corresponding variant automatically.
- is the fix in patch-CMakeLists.txt.diff a common cmake issue on os x?
Attachments (2)
Change History (10)
Changed 15 years ago by macports.org@…
| Attachment: | Portfile-awesome.diff added |
|---|
Changed 15 years ago by macports.org@…
| Attachment: | patch-CMakeLists.txt.diff added |
|---|
LINK_FLAGS export-dynamic -> dynamic
comment:1 Changed 15 years ago by nerdling (Jeremy Lavergne)
| Owner: | changed from macports-tickets@… to milosh@… |
|---|
comment:2 Changed 15 years ago by nerdling (Jeremy Lavergne)
The default variant does not cause cairo to install that way … not sure if that's what you had intended. I suggest not using that as the default, or creating a no_* variant to disable it.
comment:3 Changed 15 years ago by nerdling (Jeremy Lavergne)
| Resolution: | → fixed |
|---|---|
| Status: | new → closed |
Committed in r57461.
comment:4 Changed 15 years ago by nerdling (Jeremy Lavergne)
If the issues you highlighted crop up, let me know and I'll reopen the ticket.
comment:5 follow-up: 6 Changed 15 years ago by milosh@…
Is awesome really depending on the xcb port? I don't understand how it may use X11 cut buffers.
Second, if someone already has cairo installed without the xcb binding, awesome won't be able to build. Isn't the only solution to create a cairoxcb port (prepared to not conflict with cairo) so that we don't have a dependency on a variant?
Third, if imlib2 is a dependency, I don't believe it might be just a build dependency. Same goes for cairo.
Fourth, why move the '/' at the end of the homepage?
comment:6 follow-up: 7 Changed 15 years ago by macports.org@…
Replying to milosh@…:
Is awesome really depending on the xcb port? I don't understand how it may use X11 cut buffers.
http://planet.awesome.naquadah.org/ -> The 3.x branch
Second, if someone already has cairo installed without the xcb binding, awesome won't be able to build. Isn't the only solution to create a cairoxcb port (prepared to not conflict with cairo) so that we don't have a dependency on a variant?
I've just found some mailing list entries discussing this topic. (see also net/nedi/Portfile)
http://article.gmane.org/gmane.os.apple.macports.user/5209/match=specify+variant+depends%5flib
Is creating an additional port (here cairoxcb) the common way to deal with such dependencies?
Third, if imlib2 is a dependency, I don't believe it might be just a build dependency. Same goes for cairo.
yes, you are right. startup-notification too.
Fourth, why move the '/' at the end of the homepage?
I was confused by the missing separator in the master_sites parameter (${homepage}download/)
btw: the two diff files patch-Makefile.diff and patch-config.mk.diff can be removed.
comment:7 Changed 15 years ago by macports.org@…
btw: the two diff files patch-Makefile.diff and patch-config.mk.diff can be removed.
oh, no. they are still needed for version 2.0
awesome update to version 3.3.4