The sway-9999.ebuild uses git-r3 and checks out the 0.15 branch. This means the latest version of sway you can easily install with portage is pinned to 0.15, and isn't substantially newer than you can get from the 0.15.2 ebuild itself. With many sway bugs being closed as "fixed in 1.0", but 1.0 not yet released, it would be useful to gear toward stabilization of 1.0 when it does release by making -9999 install the master branch instead of 0.15. Reproducible: Always Steps to Reproduce: 1. Add sway-9999 and a few of its deps to package.keywords 2. emerge sway 3. run swaymsg -t get_version Actual Results: You get 0.15.2-6-g*somecommmit*, and you get all the sway bugs in 0.15 and none of the fixes (and new bugs) in master. Expected Results: You should get 1.0-beta.1-138-gd19648a3 or whatever master is at. You should get fewer 0.15 bugs, and more new bugs! :)
*** This bug has been marked as a duplicate of bug 669256 ***
