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

Pkg.submit doesn't work on windows; no which #5937

Closed
quinnj opened this issue Feb 24, 2014 · 6 comments
Closed

Pkg.submit doesn't work on windows; no which #5937

quinnj opened this issue Feb 24, 2014 · 6 comments
Labels
packages Package management and loading system:windows Affects only Windows

Comments

@quinnj
Copy link
Member

quinnj commented Feb 24, 2014

Not sure why, but it seems that mingw64/msys2 don't come with a working version of which (there seems to be something in msys2, but it said it was 32-bit for me...). Anyway, this prevents Pkg.submit from working because of the call to success("which curl') || error(.... My system does, however, have a working version of curl and commenting ou the success call allowed me to use the machinery just fine. Not sure the best way to check if a program exists on windows or if it just letting it error out is ok.

@quinnj
Copy link
Member Author

quinnj commented Feb 24, 2014

I just found a superuser question that suggests using where [cmd] as an option to just check for a program's location/existence. That's a possibility.

http://superuser.com/questions/34492/powershell-equivalent-to-unix-which-command

@StefanKarpinski
Copy link
Member

Oh Windows. Well, if you can patch this to work on Windows using where, we can merge that.

@tkelman
Copy link
Contributor

tkelman commented Feb 24, 2014

In msysgit, which is this shell script https://github.com/msysgit/msysgit/blob/master/bin/which that calls type -p $1

@vtjnash
Copy link
Member

vtjnash commented Feb 27, 2014

where is not typically available on windows according to that SO post.

I think you can just eagerly execute the curl command, since you can distinguish between process failed and process not found. (or, like WinRPM, you could use IE to download files, since that's likely to be properly configured on windows to punch through the firewall as needed, and it's always available)

@StefanKarpinski
Copy link
Member

I think you can just eagerly execute the curl command, since you can distinguish between process failed and process not found.

Yeah, that's a good point.

@quinnj
Copy link
Member Author

quinnj commented Mar 10, 2014

Should we still check for curl on unix then? And just eval on windows? I can patch this up quick if so.

JeffBezanson added a commit that referenced this issue Jun 4, 2014
Fix #5937 by removing dependency on which
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
packages Package management and loading system:windows Affects only Windows
Projects
None yet
Development

No branches or pull requests

5 participants