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

related paths #1001

Closed
skurfer opened this issue Jul 18, 2012 · 1 comment
Closed

related paths #1001

skurfer opened this issue Jul 18, 2012 · 1 comment
Assignees

Comments

@skurfer
Copy link
Member

@skurfer skurfer commented Jul 18, 2012

QSRequirements can refer to bundles or paths. I think we should be able to do something similar for relatedBundles. That is, I’d like to add support for a relatedPaths key in a plug-in’s Info.plist. The effect would be that if one of the paths exists, the plug-in will show up on the recommended list (and in the first-run spinning cube).

Why? I recently removed com.apple.Terminal from the Terminal plug-in’s relatedBundles because it doesn’t need to be recommended to all users, but surely we should be able to recommend it to some. So I was thinking we could just check for something only Terminal users are likely to have, such as /usr/local/bin. Remote Hosts could benefit from something similar, and I’m sure there are others.

@ghost ghost assigned skurfer Jul 18, 2012
@HenningJ
Copy link
Contributor

@HenningJ HenningJ commented Jul 18, 2012

QSRequirements can refer to bundles

Fix the bundles part of QSRequirements, while you're at it ;)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants