Issue 7194 - Avoid linting old jsyhydra dependency

Issue 7194 - Avoid linting old jsyhydra dependency

[kzar, 2019-01-07 14:17:04]

Patch Set 1

"Why not just delete the jshydra directory?" - Well, it'll keep getting created
again when I am bisecting with old versions of the code.

[Sebastian Noack, 2019-01-07 22:29:33]

On 2019/01/07 14:17:04, kzar wrote:
> Patch Set 1
> 
> "Why not just delete the jshydra directory?" - Well, it'll keep getting
created
> again when I am bisecting with old versions of the code.

The jshydra directory has been removed ages ago. I recommend to just call "hg
clean" after switching between revisions, which will take care of deleting the
the jshydra directory if any. But FWIW, I can hardly see why anyone would go
that far back in history in the first place, as revisions of buildtools that
still used jsHydra are vastly incompatible with adblockpluschrome for quite a
while.

[Sebastian Noack, 2019-01-07 23:29:32]

On 2019/01/07 22:29:33, Sebastian Noack wrote:
> I recommend to just call "hg clean" after switching between revisions,
> which will take care of deleting the the jshydra directory if any.

I just realized that unfortunately this won't work, due to
ensure_dependencies.py only adding dependencies to be ignored by version
control, leaving the ignores in place after the dependency has been removed.
Let's move this discussion to https://issues.adblockplus.org/ticket/7194.