#10529 closed enhancement (fixed)
[Tracker] add Package field to Info window
Reported by: | diver | Owned by: | leavengood |
---|---|---|---|
Priority: | normal | Milestone: | R1/beta2 |
Component: | Applications/Tracker | Version: | R1/Development |
Keywords: | Cc: | ||
Blocked By: | Blocking: | ||
Platform: | All |
Description (last modified by )
It would be nice to be able to identify from which package a particular file came from. For instance you're in /bin and you wan't to understand which package a certain binary belongs to. Currently there's no (easy) way to do that and Info window seems to be a logical place to get this information from. Make it clickable so it gets selected in Tracker window.
Change History (11)
comment:1 by , 11 years ago
Description: | modified (diff) |
---|
comment:2 by , 11 years ago
comment:3 by , 11 years ago
And an easy way:
~> findpaths -p /bin/notify B_FIND_PATH_PACKAGE_PATH /boot/system/packages/haiku-r1~alpha4_pm_hrev46831-1-x86.hpkg
The Tracker feature can be easily implemented using the BPathFinder
API which is also used by findpaths
.
comment:4 by , 11 years ago
How about having an additional Tracker column disabled by default? This way it would be possible to sort files by package.
comment:5 by , 10 years ago
Milestone: | R1 → Unscheduled |
---|
Moving Tracker enhancement tickets out of R1 milestone -- Tracker's source code comes from BeOS R5, so it already has all the features it did on R5.
comment:6 by , 8 years ago
Owner: | changed from | to
---|---|
Status: | new → assigned |
comment:7 by , 5 years ago
Owner: | changed from | to
---|
I will take a look at this, and maybe also adding the column as diver suggested. I am still learning my way around Tracker, but so far, so good.
comment:8 by , 5 years ago
Hi,
Rather than showing just this specific thing, I would say the Info window should have an extra tab listing all the attributes of the file. This will include the SYS:PACKAGE_FILE mentionned above and also a lot more info about the file.
I think this would be more generic and useful in other cases as well.
comment:9 by , 5 years ago
+1 to another tab with a list of all attributes (though that'd be an extra ticket...)
IMO, the clickable path to the origin package is useful enough to warrant an entry on the 1st tab.
comment:11 by , 5 years ago
Milestone: | Unscheduled → R1/beta2 |
---|
Assign tickets with status=closed and resolution=fixed within the R1/beta2 development window to the R1/beta2 Milestone
There's a non-easy way: