| Summary: | gui-apps/wf-shell-9999 should automagically rebuild after gui-libs/wf-config rebuild | ||
|---|---|---|---|
| Product: | Gentoo Linux | Reporter: | CaptainBlood <luc_pierard_de_maujouy> |
| Component: | Current packages | Assignee: | Aisha Tammy <gentoo> |
| Status: | RESOLVED WONTFIX | ||
| Severity: | normal | CC: | proxy-maint |
| Priority: | Normal | ||
| Version: | unspecified | ||
| Hardware: | All | ||
| OS: | Linux | ||
| Whiteboard: | |||
| Package list: | Runtime testing required: | --- | |
|
Description
CaptainBlood
2020-07-29 00:57:55 UTC
Only last posts of the thread matter. Thks 4 ur attention, interest & support. No it can't be added as a dependency because wayfire has an option to build wf-config as a submodule. The proper way to do this is by rebuilding emerge --ask --verbose --update --newuser @world or by doing emerge @live-rebuild (In reply to CaptainBlood from comment #0) > Thks 4 ur attention, interest & support. English please. Do I get it right that wf-config updated its soname and ABI making the new one not backwards-compatible? If yes, that's something to note for a next version release. However here as Aisha said with -9999 packages emerge -a @live-rebuild should be enough. Then do you mean wf-config is bundled to wf-shell? That shouldn't be right since wf-config exists in the tree, you should attempt to use the in-tree version. (In reply to Joonas Niilola from comment #4) > Do I get it right that wf-config updated its soname and ABI making the new > one not backwards-compatible? If yes, that's something to note for a next > version release. However here as Aisha said with -9999 packages emerge -a > @live-rebuild should be enough. > the version requirement is already there in the ebuilds so thats not what they mean. I *think* they want that everytime you rebuild the wf-config-9999 it should trigger a wayfire-9999 rebuild. which I don't know how to enforce... > Then do you mean wf-config is bundled to wf-shell? That shouldn't be right > since wf-config exists in the tree, you should attempt to use the in-tree > version. the bundled is provided as an option for doing testing and the use flag makes it *very* clear that you should not mess with the system-* flags unless you know whats happening. at this point I want to mark this as WONTFIX but I'll wait feedback. |
