-
Notifications
You must be signed in to change notification settings - Fork 414
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
Fix Electron linting errors #929
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
How much of build.sh
can we put into yarn build
. I'd love to drop that script, or at least work towards dropping it.
build/install_deps.sh
Outdated
@@ -42,6 +42,7 @@ if $LINUX; then | |||
$INSTALL build-essential libssl-dev libffi-dev libgmp3-dev python2.7-dev libsecret-1-dev curl | |||
elif $OSX && ! cmd_exists brew ; then | |||
/usr/bin/ruby -e "$(curl -fsSL https://raw.githubusercontent.com/Homebrew/install/master/install)" | |||
brew update |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
this only gets run if brew
command does not exist. so it will only update when it is installed. is that what you intended?
README.md
Outdated
|
||
### One-time Setup | ||
|
||
1. Clone this repo | ||
2. `DEPS=true ./build.sh` | ||
2. `./build.sh` |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
why did you get rid of DEPS=true?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
There's no need anymore for installing dependencies from the build script. The user should install the prerequisites listed in README.md
. That is Git, Node, and Yarn. No need anymore for Python for developing.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
it would be much better if users ran a script to install dependencies instead of following a README. that way if the dependencies change, no one has to remember to update the README
/src/main/locales | ||
/src/main/node_modules | ||
/src/renderer/dist | ||
/build/venv |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
i believe build/venv is still used (by build.sh)
.gitignore
Outdated
/daemon/build | ||
/daemon/venv | ||
/daemon/requirements.txt | ||
/.idea |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
this is here because many of us use JetBrains, which creates that dir
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I think it's better to keep project related ignore rules into the project .gitignore
and user-specific rules into the user's global .gitignore
.
/daemon/requirements.txt | ||
/.idea | ||
|
||
*.pyc |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
this has to be here while upload_assets.py is still in use. if you want to rewrite that in JS instead, then we can drop python dependency completely, which would be sweet!
|
is the app no longer built/released by teamcity? teamcity runs build.sh |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
i hope you tested this on all 3 oses, and made sure it still works with teamcity. if so, lgtm
package.json
Outdated
@@ -1,5 +1,5 @@ | |||
{ | |||
"name": "LBRY", | |||
"name": "lbry-app", |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
why did this change? will this affect the .deb package that's built? if the name changes, i think ubuntu will think its a different package...
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I changed the name to follow the norms. I'm not sure how exactly it'll behave in Ubuntu since I didn't test on it, but it should normally use the productName
field declared in the electron-builder.json
file and not the package.json
's name
.
I'll test it to be sure.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Debian does identify the app as a new package and doesn't replace the one with the previous name.
I think we should wait for the AppImage switch, which should come with the auto-update PR, before applying this change and then request Linux users that they uninstall their previous install.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
make sure you change the app name back to lbry. otherwise lgtm.
This pull request fixes #397 and:
brew update
to build script for getting latest dependencies versions.gitignore
to remove IDE specific ignores and old rules.package-json
name field to be compliant with npm and yarn rules, and adds productName to buildkeytar
withkeytar-prebuild
until feat: prebuild binaries for electron and node atom/node-keytar#67 is not merged. This simplifies the build process on Windows. There's no need anymore for Python and Windows building tools.