[INFO] Tracking projectM in Downstream Package Ecosystem

[luzpaz]

projectm is split into 2 projects (projectm and projectm-eval) on repology:

There is an open request to merge them into 1 project under projectm

Also I have begun to bump downstream repos to update to 4.0.0
Example Alpine testing (see below)

TODO

• Alpine https://pkgs.alpinelinux.org/packages?name=projectm-dev
• freshcode.club http://freshcode.club/projects/projectm

[kblaschke]

We'll release version 4.1 in a week so if all goes well, so I'd recommend waiting for this and immediately bump to this version. Reason is that 4.1 has all the great stuff for actual users of projectM, while 4.0 was basically a build system and API cleanup without a lot of real improvements.

[kblaschke]

Gentoo has been updated, I've supplied an ebuild.

[luzpaz]

I've started to bump downstream package repos. Hopeully we'll see more green labels soon 😉

[kblaschke]

Edited the OP to include projectm-eval, which is tracked separately in some distros and package managers like vcpkg.

[luzpaz]

Arch maintainer can't be contacted via the Arch package database https://archlinux.org/packages/extra/x86_64/projectm/

[kblaschke]

Arch maintainer can't be contacted via the Arch package database https://archlinux.org/packages/extra/x86_64/projectm/

That would be @BlackIkeEagle, but the last packager was someone else.

[BlackIkeEagle]

Yeah, projectm is hold back because other things still depend on the 3.x version without seemingly much progress

[kblaschke]

Yeah, projectm is hold back because other things still depend on the 3.x version without seemingly much progress

One solution would be introducing a new package libprojectm for projectM 4 if Arch doesn't support slotted installs (projectM 3 and 4 can be installed side by side). This would allow keeping the 3.1.12 release as-is, while already introducing the new package and transitioning depedencies one by one as they're updated to use the new release. Adding "lib" to the package name would also distinguish it from previous releases, which contained a number of applications in the same codebase, which have been removed/split out in projectM 4.0.

qmmp for example already supports projectM 4, I'm working on getting the VLC plug-in updated (will probably not be shipped until the VLC 4.0 release) and there's a WIP PR for the Kodi plug-in as well.

[C0rn3j]

@luzpaz I'd suggest adding ?exclude_unsupported=1 to the repology view, so only relevant OSs are shown: https://repology.org/badge/vertical-allrepos/projectm.svg?exclude_unsupported=1

How did you do the 3 column view badge?

[luzpaz]

I'd suggest adding ?exclude_unsupported=1

Done!

How did you do the 3 column view badge?

?columns=3