- Notifications
You must be signed in to change notification settings - Fork384
Add Capture One and update adobe apps#722
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 ourterms of service andprivacy statement. We’ll occasionally send you account related emails.
Already on GitHub?Sign in to your account
base:main
Are you sure you want to change the base?
Uh oh!
There was an error while loading.Please reload this page.
Conversation
Signed-off-by: Yoann Laissus <yoann.laissus@gmail.com>
for more information, seehttps://pre-commit.ci
LDprg commentedSep 9, 2025
@oskardotglobal I am not sure about just adding new Adobe stuff. They tend to change they naming from time to time. Replacing don't seem like an option since old Adobe versions might still be used out there (Adobe doesn't deploy new versions to every user at the same time). However I am not sure, whether there is a better way to do this than just keep two Adobe versions around. |
Arakmar commentedSep 9, 2025
@LDprg I agree, it will be complex to maintain if they decide to change the path every year... |
LDprg commentedSep 10, 2025
Bash Arrays seem to be a good solution for this. This way we could add alternative paths, which is not a problem, since you won't install multiple versions. @oskardotglobal what do you think? |
oskardotglobal commentedSep 11, 2025
Arrays are a good idea, the only issue with that would be if a user has two versions |
Creative Cloud is now installing the 2025 version of some Adobe apps
Their naming scheme is really a mess...
Maybe some old Adobe app versions can be removed ?