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

Mention Windows in README. #54

Open
fabioz opened this issue May 28, 2013 · 6 comments
Open

Mention Windows in README. #54

fabioz opened this issue May 28, 2013 · 6 comments

Comments

@fabioz
Copy link

fabioz commented May 28, 2013

I think it may be nice to say that windows is unsupported in the README -- I'm trying to discover if it should work there -- even if I need to get cygwin, but so far it seems it's not, so, it may be nice to at least state that in the README so that windows users (such as myself) know that before downloading it...

@tomByrer
Copy link

tomByrer commented Jul 4, 2013

Is Windows still unsupported, or has someone managed to make it work please?

@trogdoro
Copy link
Owner

trogdoro commented Jul 4, 2013

Still no Windows support. I just added a note to the README drawing
attention to this.

It looks like the daemons gem actually works on Windows. What's needed is
a way on Windows to communicate between processes in a way that requires
proper permissions. Meaning just that the process making the call is owned
by the user, and can't be some unprivileged process. Or is this even
relevant on Windows - I'm not really sure.

Any ideas? There was another thread about this, but it trailed off.

--Craig

On Thu, Jul 4, 2013 at 9:53 AM, tomByrer [email protected] wrote:

Is Windows still unsupported, or has someone managed to make it work
please?


Reply to this email directly or view it on GitHubhttps://github.com//issues/54#issuecomment-20486123
.

@ghost
Copy link

ghost commented Jul 1, 2014

Just another ping for Windows support. Is there a better issue to track this?

@vprimachenko
Copy link

@voltagex there is even a pull request #68

@iivmok
Copy link

iivmok commented Jul 8, 2014

Meaning just that the process making the call is owned by the user, and can't be some unprivileged process

@trogdoro In windows, every process is (normally) launched with users privileges. So if user launches Xiki and Xiki launches git.exe, then Git will be running with users privileges.

@tomByrer
Copy link

tomByrer commented May 1, 2017

Bash for Windows?...

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

No branches or pull requests

5 participants