Linking: chrome-mac/Chromium.app/Contents/Versions/.0/Chromium amework/Libraries -> Versions/Current/Libraries Linking: chrome-mac/Chromium.app/Contents/Versions/.0/Chromium amework/Internet Plug-Ins -> Versions/Current/Internet Plug-Ins Linking: chrome-mac/Chromium.app/Contents/Versions/.0/Chromium amework/Helpers -> Versions/Current/Helpers So I suggest we should put the download process in the install process, but allow users to disable it (not familiar with pip, but is it doing setting up some ENV variable before installation?) if they need a different chromium.įor the potential risk I mentioned, once the download process is being processed in the install phase, it won't be a problem anymore ( if the download fails, the deployment will not begin at the first place)Īnd for my current solution, it works but not reliable, since I shouldn't rely on the lib's implementation details it's another breakpoint once the lib changes it's API changes this actually leads to the question that what is the main use case this lib is targetting and it should try to meet the main use case well first and then provide ways to achieve other cases.įrom my perspective (my case), I don't want to worry too much about the download process (especially which version I need to use) but at the same time, the lib shouldn't add extra risk of causing my online service fail.
0 kommentar(er)
