Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

installation path column for installed packages #278

Open
OlafHaag opened this issue Aug 15, 2015 · 7 comments
Open

installation path column for installed packages #278

OlafHaag opened this issue Aug 15, 2015 · 7 comments
Labels
0 - Backlog Issue is accepted, but is not ready to be worked on or not in current sprint Improvement Issues that enhances existing functionality, or adds new features

Comments

@OlafHaag
Copy link

With chocolatey I'm not always sure where packages, especially with natice installers, get installed to. So it would be great if there was a column showing the installation path in the "This PC" category. In addition to that a context menu with "show in explorer" would be helpful, too.

@OlafHaag OlafHaag changed the title installation path colum for installed packages installation path column for installed packages Aug 15, 2015
@gep13
Copy link
Member

gep13 commented Aug 15, 2015

I don't think that this is something that Chocolatey has knowledge of either. @ferventcoder is this something that can be exposed?

@OlafHaag
Copy link
Author

At least for some packages with installers I found the installation path by looking inside the "\chocolatey.chocolatey\packagename.version.registry" (if there is one) for . So I guess it could be exposed. Unfortunately for some MSI packages I only get a cryptic key which is the id i presume. It also tells you the installertype like "MSI", "InnoSetup", "Unknown" or "Custom".
Well, as for zip packeges, maybe the .files or the chocolatey.log is any good?

@ferventcoder
Copy link
Member

Yes, choco has knowledge of where it installs given the registry snapshot gathers that information.

@gep13
Copy link
Member

gep13 commented Aug 16, 2015

@ferventcoder interesting... so this could be something that we expose in ChocolateyGUI. 👍

@RichiCoder1 RichiCoder1 added Up for Grabs Issues that are available by the community to work on Improvement Issues that enhances existing functionality, or adds new features :UI labels Jun 3, 2016
@RichiCoder1 RichiCoder1 added this to the Future milestone Jun 3, 2016
@RichiCoder1
Copy link
Contributor

I don't think this is something we'd get around to for a while, but if someone else would be interested, go for it.

@gep13
Copy link
Member

gep13 commented Apr 23, 2019

This is related to this issue: #597

One is for a change to the package details page, and the other for list view.

@pauby pauby removed Up for Grabs Issues that are available by the community to work on Need Details labels Jun 28, 2023
@pauby pauby removed this from the Future milestone Jun 28, 2023
@pauby pauby added the 0 - Backlog Issue is accepted, but is not ready to be worked on or not in current sprint label Apr 16, 2024
@Mugane
Copy link

Mugane commented Aug 5, 2024

Am I correct in my assessment that after ten years this has yet to be done?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
0 - Backlog Issue is accepted, but is not ready to be worked on or not in current sprint Improvement Issues that enhances existing functionality, or adds new features
Projects
None yet
Development

No branches or pull requests

6 participants