Bug 659588

Summary:	media-sound/moodbar - New package (new upstream?) version
Product:	Gentoo Linux	Reporter:	Simon <sur3>
Component:	New packages	Assignee:	Default Assignee for New Packages <maintainer-wanted>
Status:	UNCONFIRMED ---
Severity:	normal	CC:	Sander.Sweers
Priority:	Normal
Version:	unspecified
Hardware:	All
OS:	Linux
URL:	https://github.com/exaile/moodbar
See Also:	https://bugs.gentoo.org/show_bug.cgi?id=629184
Whiteboard:
Package list:		Runtime testing required:	---
Attachments:	media-sound/moodbar-9999.ebuild

Description Simon 2018-06-29 12:27:54 UTC

There is a dropin moodbar version that doesn't depend on gstreamer 0.10, this resolves #629184

I put https://github.com/exaile/moodbar in the URL because that is the version of exaile extracted from clementine, which is therefore more up-to-date than the Amazon plugin related version at https://github.com/Mazhoon/moodbar
Also I suppose the only usecase of this program is probably exaile now, therefore it makes sense to use the version from the exaile developers.

Reproducible: Always

Comment 1 Sander Sweers 2018-06-29 13:02:14 UTC

Created attachment 537700 [details]
media-sound/moodbar-9999.ebuild

If you want the 1.0 release save it as moodbar-1.0.ebuild

Comment 2 Sander Sweers 2018-06-30 10:22:37 UTC

I added meson build to Mazhoons moddbar [1] but ... reading the release note for the latest version [2] does not give me much confidence...

Both do the job but I think the exaile version for now is better option as it looks actually maintained.

[1] https://github.com/Mazhoon/moodbar/pull/1
[2] https://github.com/Mazhoon/moodbar/releases/tag/v0.1.4

Comment 3 Simon 2018-07-01 17:41:52 UTC

I thought so too that the exaile version is preferable.
The only downside of the exaile version in my opinion is that the exaile version uses this weird meson system and the Mazhoons version has a clean cmake build system, why did you create a pull request for this meson thing? You probably should have created a cmake pull request for the exaile version instead.. :D

Comment 4 Simon 2018-07-02 14:09:32 UTC

Why this "new upstream?" in the title?
To clarify the history is as follows:

Amarok -> Clementine -> Exaile

The Amarok code was not maintained anymore, but instead of just updating it the Clementine people built it directly linked with their Program, the Exaile people therefore extracted the maintained code from clementine and build it into an independent program again. Even if the old upstream would went up-to-date, it would be outdated as the Clementine version used as base for the Exaile version had more maintenance all the time off course.