-
Notifications
You must be signed in to change notification settings - Fork 18
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
RFP - Oracle SQL Developer #383
Comments
please do! |
Tempted to bite but this one will be trick to do because download requires clicking boxes for licence and then logging in. Hosting the package within the nupkg would be possible technically but it's Oracle, so legally that would want to be very clearly defined and agreed in writing. |
Well, since the license doesn't explicitly allow distribution of the installer, it certainly can't be embedded without permission from Oracle. If there is a requirement to click the accept license boxes, this certainly complicates things. But maybe it could be worked around similiar in how it's done with the jre and jdk packages. Anyhow, I'll also mark this with an |
"requirement to click the accept license boxes" But in next step we need some account credentials Is it okay to put these dummy account credentials into nupkg? |
I think Oracle may dislike that, if they start seeing floods of downloads from one account they may block it or even worse, they might call the legal department to send cease and desist letters. They might even put a captcha to weed out scripts. I think it would be more successful if the nupkg could pass parameters for specific oracle credentials added per user and submit them through the site. It would not be an anonymous download but at least it would be silent. |
This StackExchange describes a way to download JDK without sign-up:
maybe it's applicable for this package too? |
Can we progress this package and remove the 'Blocked Upstream' label given the comment by @JonasDralle ? |
@pauby yeah, we probably can do that |
I'm new to chocolatey but would be interested in taking a shot at this one. I've played around with this a little bit, and it seems doable using a technique similar to what @JonasDralle proposed to get around having to click the license agreement. The issue is that at some point you have to have a (free) Oracle account to download the file. Is it acceptable to prompt for credentials during a chocolatey install (Get-Credential or similar) and/or allow the credentials to be passed in as argument to the install? |
@wcarson the install should be silent. If it is absolutely required you could make sure the details are passed as package parameters. |
Or at least unattended (silent would mean nothing is shown during install) |
Unattended is a better description :) |
Hi. I pushed an initial version for review. To handle the Oracle Account requirement, the package requires that the credentials be specified as package params: [removed attachment - package is now available here: https://chocolatey.org/packages/oracle-sql-developer] |
For Oracle SQL Developer 19.1.0, I made a commit in a fresh branch at jpluimers/chocolatey-packages@796b1e4 Detailled change description and process is in the commit. Two questions:
I am not sure for how long I will be using Oracle SQL Developer, but it is likely not for years, so I might not be able to provide updates for future Oracle SQL Developer versions. (Edit: I'm really new to chocolatey, but not new to software development; I read through the Chocolatey Testing Environment VM that @wcarson mentioned, but doing a deep dive into vagrant is too much for me right now, this apart from the verifier service link in it not working at all since december 2017 makes me feel a lot of it is outdated with a steep learning curve ahead) |
Run the package through the Chocolatey Test Environment. However I noted your comments about it - the Vagrant environment is simply a bare, unpatched (for a reason) Windows Server 2012 R2 server. So if you can spin one of those up you can test your package on there. Ordinarily we woudl recommend not testing on your machine as you may not be able to pick up all the dependencies required. However as this is a change to an existing package, as long as you are mindful of it, you should be able to get away with testing it there.
If you're confident the code / package works then contacting the maintainer and submitting the PR would be a good way to start. This is the reason why we ask maintainers to provide a You might want to reach out to Gitter if you need more help. |
Hidden dependency: Internet Explorer needs to be initialized
Can be solved by opening IE and clicking a few boxes. The far more pressing issue is that the package does not work on 64 Bit machines:
The log contains credentials which can be used by anyone for testing purposes: |
Database Development tool
common in enterprise enviroment
used every day by my team
latest available via http://www.oracle.com/technetwork/developer-tools/sql-developer/downloads/index.html
The text was updated successfully, but these errors were encountered: