Prior to orphan request PRQ#49707, the package was also flagged. The maintainer unflagged without taking action. The maintainer has also written a reply to the orphan request, so is fully aware of the issue.
As said, nestopia does not need GLU, it should not be my responsibility to fix upstream's or other package's bugs.
Despite claims that this is an issue with fltk, maintainer has not opened an issue report for that package. (None appears in search results at bugs.archlinux.org.) Also, tools, such as namcap, do not identify reliance of fltk on any glu-related packages.
You are likely capable of opening a bug yourself there, since writing this email does not take much longer...
Do you add the `linux` dependency to all your packages, because without the kernel nothing would run?Even if fltk did have an unnamed dependency on glu, Arch package guidelines state: "Do not rely on transitive dependencies". So a prudent maintainer, especially given the error reports, would still choose to include glu in the dependency list.
Given that the current maintainer is willfully keeping this package in a broken state for about 2.5 years, it should be orphaned immediately so that a responsible maintainer may take over.
Your whole effort is a bit misdirected, I suggest you try to resolve some real problems in your free time.
best regards,
carstene1ns