-
-
Notifications
You must be signed in to change notification settings - Fork 14.2k
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
atom*: drop #258440
atom*: drop #258440
Conversation
Ref to: #254798 |
ofborg-eval is unhappy due to various dependencies on atomEnv in nixpkgs. |
I just checked a few atomEnv usages and it mostly seems like a legacy artifact before electron was really a thing and can be completely removed in some cases. |
I started all touched applications and they started up properly but I never went past login screens. |
It would be nice to add a notice about Pulsar being the new Atom fork ;) |
We can write that into the error message but I don't think we can just alias it without any user action required. But IMO people should just migrate to vscode ;) |
8e278d7
to
ecf3bf8
Compare
Please re-order the commits to put the atomEnv removal at the end (after its usages were removed). Otherwise LGTM. |
ecf3bf8
to
244be72
Compare
Likely only me and a handful of others are affected by this. LGTM Result of 34 packages marked as broken and skipped:
37 packages built:
|
Waiting for ofborg-eval to complete on the last version of this PR out of caution, I'll merge once that's finished. |
Description of changes
https://atom.io redirects to https://github.blog/2022-06-08-sunsetting-atom/ which explicitly states
No more security updates
and the repo is archived since last November. This means atom is probably vulnerable to the recent libwebp and libvpx CVEs and probably more.Things done
sandbox = true
set innix.conf
? (See Nix manual)nix-shell -p nixpkgs-review --run "nixpkgs-review rev HEAD"
. Note: all changes have to be committed, also see nixpkgs-review usage./result/bin/
)