Remove special handling for linter package in generate_package_config #53400
Labels
analyzer-linter
Issues with the analyzer's support for the linter package
area-infrastructure
Use area-infrastructure for SDK infrastructure issues, like continuous integration bot changes.
The linter package has been moved from third_party/pkg/linter in DEPS to pgk/linter in the repo.
A workaround was added to generate_package_config to handle the case that both copies of linter were present.
Linter was removed from DEPS on 2023/08/28, so we can remove this workaround about one week later.
All the bots should have refreshed, and removed it from their caches.
Developers may still have a copy in third_party unless they have run "gclient sync -D". They will have
seen warning messages saying that linter has been removed, and to run this command, if they
have synced since it was removed from DEPS.
I don't think an added warning, besides the one that already comes from gclient sync and the failure
of generate_package_config, saying the the linter package was found in two places, is needed.
Move of linter into the Dart SDK repo is tracked at (closed) issue:
dart-lang/linter#4411
The text was updated successfully, but these errors were encountered: