Community Packages

Please read this before reporting a bug:
https://wiki.archlinux.org/title/Bug_reporting_guidelines

Do NOT report bugs when a package is just outdated, or it is in the AUR. Use the 'flag out of date' link on the package page, or the Mailing List.

REPEAT: Do NOT report bugs for outdated packages!
Tasklist

FS#62000 - [fltk] should not include games

Attached to Project: Community Packages
Opened by André Miranda (andreldm) - Wednesday, 13 March 2019, 22:52 GMT
Last edited by David Runge (dvzrv) - Saturday, 20 June 2020, 19:13 GMT
Task Type General Gripe
Category Packages
Status Closed
Assigned To David Runge (dvzrv)
Architecture All
Severity Low
Priority Normal
Reported Version
Due in Version Undecided
Due Date Undecided
Percent Complete 100%
Votes 6
Private No

Details

Since fltk-1.3.5 games are now part of the package, I think this is a mistake, now users that have installed some app the depends upon fltk will have their app list cluttered by those games. This is also valid for fluid, which was already part of fltk package, even though it's not part of the library, but a development tool.
Therefore I request to exclude games and fluid from the fltk package, if anyone cares so much about them, AUR packages should do.
This task depends upon

Closed by  David Runge (dvzrv)
Saturday, 20 June 2020, 19:13 GMT
Reason for closing:  Fixed
Additional comments about closing:  Examples are in separate package since 1.3.5-2
Comment by Marc Sven Schulte (msschulte) - Thursday, 14 March 2019, 15:37 GMT
I also confirm the behavior, the games should be outsourced.
Comment by Alberto Salvia Novella (es20490446e) - Friday, 15 March 2019, 04:11 GMT
Just saw the bug myself.
Comment by David Runge (dvzrv) - Friday, 15 March 2019, 12:12 GMT
The cmake based setup (and also the former autoconf based setup) is still pretty flawed. I have opened several bug reports ([1] [2] [3]) regarding these problems (als in hinsight of packaging shared libraries appropriately).
As the man pages of the games are installed by default and also the games (i.e. examples) are built by default, this seems to be upstream intention. However, I also don't see much of a use-case for developers.
Please take this upstream though and support transitioning towards a more sane build setup. I'll be happy to incorporate upcoming changes!

[1] https://github.com/fltk/fltk/issues/20
[2] https://github.com/fltk/fltk/issues/22
[3] https://github.com/fltk/fltk/issues/23
Comment by Bachsau (Bachsau) - Wednesday, 20 March 2019, 00:25 GMT
I just got annoyed by the same thing. Even if upstream should have some weird intentions: Neither games nor their man pages or any development tool should be part of a toolkit package. As this packages is marked as a replacement for fltk-games, it seems to me that they were available in a separate package before, which is a good solution. I don't see a reason why you should not split them, even if upstream thinks otherwise.

Loading...