Bug 276245 - x11-wm/compiz: x11-wm/compiz and friends moved to new upstream
Summary: x11-wm/compiz: x11-wm/compiz and friends moved to new upstream
Status: Closed FIXED
Alias: None
Product: Ports & Packages
Classification: Unclassified
Component: Individual Port(s) (show other bugs)
Version: Latest
Hardware: Any Any
: --- Affects Only Me
Assignee: Kurt Jaeger
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2024-01-10 18:23 UTC by Tomoaki AOKI
Modified: 2024-02-09 09:34 UTC (History)
4 users (show)

See Also:
pi: maintainer-feedback+


Attachments
git diff for x11-wm/libcompizconfig (689 bytes, patch)
2024-01-17 20:00 UTC, Chris Hutchinson
portmaster: maintainer-approval+
Details | Diff

Note You need to log in before you can comment on or make changes to this bug.
Description Tomoaki AOKI 2024-01-10 18:23:59 UTC
Now upstream of x11-wm/compiz and its friends are switched.
But git ports 022a98692f0c806003f671e5037ca21a02431d6b for x11-wm/libcompizconfig deprecated it as Abandoned project.

The official websites are below.
Both seems to be under development, not abandoned.

For legacy 0.8 branch:
  https://github.com/compiz-reloaded

For new 0.9 branch:
  https://launchpad.net/compiz

Unfortunately, contents of distfiles for currently ported 0.8.8 seems to be different between one in ports tree and the one in new (legacy) upstream.
Maybe the maintainer would changed something for FreeBSD, but unfortunately, I have not enough time and skill to investigate further.

Can someone look into it and port again?
Current upstream for legacy 0.8 branch seems to be forked from original one by people who don't like changes on new 0.9 series. So whether to switch to would be need consideration.

CC'ing bofh@ who deprecated.
Comment 1 Chris Hutchinson 2024-01-17 20:00:50 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
Comment 2 Tomoaki AOKI 2024-01-17 22:47:23 UTC
(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
Comment 3 commit-hook freebsd_committer freebsd_triage 2024-02-08 09:00:17 UTC
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(-)
Comment 4 Tomoaki AOKI 2024-02-08 09:51:05 UTC
(In reply to commit-hook from comment #3)

Confirmed. Thanks for taking this, Kurt!
Comment 5 Daniel Engberg freebsd_committer freebsd_triage 2024-02-08 23:20:37 UTC
This should be moved to compiz-reloaded as mentioned before and have patches upstreamed.
Comment 6 Chris Hutchinson 2024-02-09 00:58:35 UTC
(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
Comment 7 Tomoaki AOKI 2024-02-09 09:34:41 UTC
(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.