Skip to content
This repository has been archived by the owner on Feb 19, 2019. It is now read-only.

[Documentation] Document decision for Shims versus other technologies #633

Open
dhilgarth opened this issue Dec 3, 2014 · 2 comments
Open

Comments

@dhilgarth
Copy link

I am wondering why you aren't simply using shortcuts, soft or hard links instead of the generation of shim executables. This seems to be a much simpler way with less complications.

Why did you decide against it?

@ferventcoder
Copy link
Contributor

Apologies if I don't give you a direct answer but after answering the question several times already (all are searchable and readily readable) - I think we just need to document it on the wiki.

@ferventcoder ferventcoder changed the title Question about shims: Why not just a shortcut or hard link? [Documentation] Document decision for Shims versus other technologies Dec 3, 2014
@ferventcoder
Copy link
Contributor

Also, questions work out much better on the mailing list - chocolatey at googlegroups dot com.

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

No branches or pull requests

2 participants