Skip to content

Conversation

ymeine
Copy link

@ymeine ymeine commented Apr 29, 2025

In addition to what is described in the linked issue, it also fixes a few other things:

  • remove the right service during uninstall by using the service name gotten from PowerShell
  • stop only the processes linked to that application

Those fixes are meant to handle a proper cohabitation of different versions of Everything, no matter how many processes or services they each have.

Closes #2216

Copy link
Contributor

All changes look good.

Wait for review from human collaborators.

everything-alpha

  • Description
  • License
  • Hashes
  • Checkver
  • Autoupdate

…service (fix ScoopInstaller#2216)

In addition to what is described in the linked issue, it also fixes a few other things:

- remove the right service during uninstall by using the service name gotten from PowerShell
- stop only the processes linked to that application

Those fixes are meant to handle a proper cohabitation of different versions of Everything, no matter how many processes or services they each have.
@ymeine ymeine force-pushed the issue-2216-everything-alpha-service-check branch from 3eaf78b to 6f51e0e Compare April 30, 2025 13:09
@HUMORCE
Copy link
Member

HUMORCE commented Jun 6, 2025

It should align with extras/everything.

@ymeine
Copy link
Author

ymeine commented Jun 6, 2025

@HUMORCE extras/everything has a different implementation which I think has the same issues as described in #2216.

I guess you meant the opposite then, that extras/everything should align with this new implementation of versions/everything-alpha?

In that case, do you mean that I should create an equivalent PR for extras/everything, so that you would eventually merge both around the same time to keep consistency?

If that is the case, the current PR here would require a proper review and approval first, so that work is not duplicated with the upcoming PR for extras/everything (otherwise comments and updates may come in twice).

@HUMORCE
Copy link
Member

HUMORCE commented Jun 6, 2025

In that case, do you mean that I should create an equivalent PR for extras/everything

Yes, label alpha-specific code with commented separately as possible, for better maintainability

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

[Bug]: everything-alpha does not check properly for the existence of the Everything service
2 participants