On Friday, November 25, 2022 at 8:47:08 AM UTC+1 igi...@gmail.com wrote:

> Hi,
>
> Yes, I saw that, but was hoping to find something even more readily 
> available, as I said, preferably a .zip file hosted somewhere?
>
> Why? Because I use scoop package manager ( scoop.sh ). It already contains 
> tortoisesvn, but not tortoisegit. I'm trying to create a new 
> tortoiseoverlays package so that both tortoisesvn and tortoisegit can use 
> tortoiseoverlays as a dependency. I got it to work, but now I just need to 
> add the rest of the icon packs. I can manually zip and host the icons if I 
> really have to. But then it becomes just one more thing I have to maintain. 
> Hoping for an easier solution. Hope this makes sense. BTW, scoop is great. 
> I much prefer it over chocolatey or winget.
>

both TSVN and TGit use the same TortoiseOverlays package. It won't be 
installed twice even if you have both TSVN and TGit installed. That's how 
merge modules work. You should not create your own packages from those. 
Because it's too easy to make a mistake. The way this works now is that msi 
takes care of the overlays merge module and makes sure it's only installed 
once, but it also keeps a dependency count on it. So if you install TGit 
and then TSVN (or vice versa), the overlays component is installed first 
with TGit, and then when you install TSVN the reference count is increased 
for the overlays module. This ensures that if you deinstall one of them, 
the overlays module stays installed until both TGit and TSVN are 
uninstalled.

Also, the Overlays module is used by other Tortoise clients as well (e.g. 
TortoiseHg, and even TortoiseCVS in case someone is still using that). 

-- 
You received this message because you are subscribed to the Google Groups 
"TortoiseSVN" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to tortoisesvn+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/tortoisesvn/3672cd9c-8e0f-4d1e-9336-0b34676afea0n%40googlegroups.com.

Reply via email to