Opened 21 months ago
Closed 6 months ago
#18274 closed enhancement (fixed)
HaikuDepot: remove email link
Reported by: | humdinger | Owned by: | apl-haiku |
---|---|---|---|
Priority: | normal | Milestone: | R1/beta5 |
Component: | Applications/HaikuDepot | Version: | R1/beta4 |
Keywords: | Cc: | ||
Blocked By: | Blocking: | ||
Platform: | All |
Description
At the bottom left corner, below the screenshot and above the homepage URL, there's an email icon labelled "<no info>". No package seems to populate that email field. Until they do, how about removing that email line in HaikuDepot's GUI? Added bonus: leaves more space for the screenshot.
Change History (5)
comment:1 by , 21 months ago
comment:2 by , 21 months ago
On the linked hompage there usually is a link to the bug tracker. In case of ports, you'd have to point to the project's bug tracker and the haikuports tracker. You also have to explain for which kind of bugs to use one or the other. Whatever we link, people will keep asking on the forums and post their bugreports there.
comment:3 by , 21 months ago
Linking to just the haikuports tracker sounds better then, if it really is an upstream problem users can be directed then, but it is nicer initially to have a single point of contact.
comment:4 by , 21 months ago
Alright. How about this then: don't show the email icon and <no info> if there isn't such info. Show the a bugtracker icon + url, if there's such a thing in the package.
Currently there's just one url, that is "HOMEPAGE" in recipes. I suppose someone needs to add a new "BUGTRACKER" constant to haikuporter and all recipes.
Can we remove the empty email field as first step?
comment:5 by , 6 months ago
Milestone: | Unscheduled → R1/beta5 |
---|---|
Resolution: | → fixed |
Status: | new → closed |
Fix merged in hrev57756.
If the place is left, I'd rather see there the correct URL to report a bug. The URL given leads to a project homepage that can be dead or only informative. Even if there's a bug tracker, they may not accept bugs coming from a Haiku user. For example because they didn't make the port. Only the packager knows if the sources are requiring patches to build and if they were or not sent upstream.
Every depot has a tracker, so why not indicate the URL to it by default? In some cases, native apps mainly, it could be more precise and be the project tracker URL.
Of course, we could continue to wait that people ask on the forum but it's not efficient, is it?