Confirmed users
2,473
edits
| Line 83: | Line 83: | ||
A similar directory structure is proposed for Linux and Mac as well. | A similar directory structure is proposed for Linux and Mac as well. | ||
[[User:LawrenceMandel|LawrenceMandel]] The example above adds | [[User:LawrenceMandel|LawrenceMandel]] The example above adds 19 characters to the path. Is there any risk of hitting the Windows path limit of 255 chars due to this addition? | ||
Here's the plan of attack for this problem: | Here's the plan of attack for this problem: | ||
# Make the stub executable aware of this directory layout. | # Make the stub executable aware of this directory layout. | ||
#* The installer will look for directories named \d+\.[a-fA-F\d]{40}. | |||
#* If more than such a directory is found, the stub executable will do a version comparison and pick the newer one. | |||
#* If such a directory is found, the stub executable will load DLLs from that directory instead of its own. Platform specific details TBD. | |||
#* If such a directory is not found, everything will proceed as it does today. | |||
#* If a version specific directory is found, that will serve as the process directory for all intents and purposes from that point on. | |||
# Change the packaging step to actually package stuff under that structure. | # Change the packaging step to actually package stuff under that structure. | ||