Opened 20 months ago
Closed 19 months ago
#67097 closed defect (fixed)
chromedriver @110.0.5481.77: cannot be rebuilt with port rev-upgrade since it seems to require Uniform Type Identifiers framework in macOS 10.15
Reported by: | JD-Veiga | Owned by: | catap (Kirill A. Korinsky) |
---|---|---|---|
Priority: | Normal | Milestone: | |
Component: | ports | Version: | 2.8.1 |
Keywords: | Cc: | ||
Port: | chromedriver |
Description
Hi,
I cannot re-built chromedriver@110.0.5481.77 after upgrading other packages. This re-building seems to require Uniform Type Identifiers framework. This framework is not available in macOS 10.15 Catalina but in macOS 11 and later (according https://developer.apple.com/documentation/uniformtypeidentifiers).
Running port -v rev-upgrade
produces:
---> Scanning binaries for linking errors Could not open /System/Library/Frameworks/UniformTypeIdentifiers.framework/Versions/A/UniformTypeIdentifiers: Error opening or reading file (referenced from /opt/local/bin/chromedriver) ---> Found 1 broken file, matching files to ports ---> Found 1 broken port, determining rebuild order
Is it possible to support chromedriver in versions earlier than macOS 11?
Thank you.
Change History (4)
comment:1 Changed 20 months ago by catap (Kirill A. Korinsky)
comment:2 Changed 20 months ago by JD-Veiga
I see. I also think that first option (mark chromedriver as broken on macOS earlier than 11) seems the only viable solution.
I really do not know if someone could be interested in installing previous versions of chromedriver (and use it with earlier versions of Chrome). This option is currently not provided via macports. (Personally, I do not see that possibility very useful... but who knows...)
Thank you.
comment:3 Changed 20 months ago by jmroot (Joshua Root)
Cc: | kirill@… catap removed |
---|---|
Owner: | set to catap |
Status: | new → assigned |
comment:4 Changed 19 months ago by catap (Kirill A. Korinsky)
Resolution: | → fixed |
---|---|
Status: | assigned → closed |
Here I see two possible ways to solve this problem: (1) is to mark chromedriver as broken on everything before macOS 11, and (2) is to keep the legacy version.
As far as I can remember, Chrome is quite persistent in trying to update itself, and chromedriver requires the same version of Chrome, which makes the second option quite questionable to say at least.