Summary: | x11-wm/compiz: x11-wm/compiz and friends moved to new upstream | ||||||
---|---|---|---|---|---|---|---|
Product: | Ports & Packages | Reporter: | Tomoaki AOKI <junchoon> | ||||
Component: | Individual Port(s) | Assignee: | Kurt Jaeger <pi> | ||||
Status: | Closed FIXED | ||||||
Severity: | Affects Only Me | CC: | bofh, diizzy, pi, portmaster | ||||
Priority: | --- | Flags: | pi:
maintainer-feedback+
|
||||
Version: | Latest | ||||||
Hardware: | Any | ||||||
OS: | Any | ||||||
Attachments: |
|
Description
Tomoaki AOKI
2024-01-10 18:23:59 UTC
Created attachment 247732 [details]
git diff for x11-wm/libcompizconfig
OK here's a patch to put this back on the map.
There are indeed 2 separate sources. You've correctly
captured the attitude that separates them. I can currently
only speak to the 0.8.8 source that is the original. Which
is NOT abandoned. However low the activity may seem.
Anyway, all political issues aside. The attached patch
makes for a fully functional port for x11-wm/libcompizconfig.
Thank you for all your time and attention.
--Chris
(In reply to Chris Hutchinson from comment #1) Thanks! Looking forward to this hit the tree. For portmgr: I'm actually using compiz and some more people, at least another, would do, too. It can be seen on the discussion about workarounds for dropped support of gconf [1]. [1] https://lists.freebsd.org/archives/freebsd-ports/2022-June/002082.html A commit in branch main references this bug: URL: https://cgit.FreeBSD.org/ports/commit/?id=cc82c35e6975719aeaad389610ad4228db91c3cc commit cc82c35e6975719aeaad389610ad4228db91c3cc Author: BChris Hutchinson <portmaster@bsdforge.com> AuthorDate: 2024-02-08 08:58:39 +0000 Commit: Kurt Jaeger <pi@FreeBSD.org> CommitDate: 2024-02-08 08:59:10 +0000 x11-wm/libcompizconfig: remove deprecation, new upstream is coming PR: 276245 Author: Chris Hutchinson <portmaster@bsdforge.com> Date: Thu Feb 8 09:58:39 2024 +0100 x11-wm/libcompizconfig/Makefile | 5 +---- 1 file changed, 1 insertion(+), 4 deletions(-) (In reply to commit-hook from comment #3) Confirmed. Thanks for taking this, Kurt! This should be moved to compiz-reloaded as mentioned before and have patches upstreamed. (In reply to Daniel Engberg from comment #5) Both versions have 2 different objectives. Neither objective is wrong. I've chosen the original branch. The issues/problems raised in the other branch don't exist in the original branch. I might argue that that speaks to my chosen branch being a better choice. Either way; there doesn't appear to be a good reason to move to the other branch. GitHub has a much higher traffic volume than Launchpad. So any flaws that may exist will more likely be discovered through GitHub than Launchpad. Compiz is not broken. Let's not try to fix it. :) --Chris (In reply to Chris Hutchinson from comment #6) Unfortunately, one thing needed to be fixed on FreeBSD ports, the lack of ccsm. It was deleted as of python27 dependencies axing, so porting newer one which is fixed for python3 is needed, which I have not enough ability/knowledge and time to port. I think it seems to be better cherry-picking from compiz-reloaded (legacy 0.8 branch) what are needed. Upgrading whole compiz related ports would be different matter (next step to consider). But I currently cannot believe choosing 0.9 branch is a good direction to go. |