Opened 9 years ago

Closed 9 years ago

Last modified 9 years ago

#45850 closed submission (fixed)

chromedriver 2.12 new port submission

Reported by: rockettj@… Owned by: ryandesign (Ryan Carsten Schmidt)
Priority: Normal Milestone:
Component: ports Version: 2.3.2
Keywords: Cc:
Port: chromedriver

Description

I've put together a Portfile for installing chromedriver. This is a WebDriver implementation for driving Google Chrome for testing purposes (i.e. with Cucumber/Watir).

Attachments (1)

Portfile (1.3 KB) - added by rockettj@… 9 years ago.

Download all attachments as: .zip

Change History (5)

Changed 9 years ago by rockettj@…

Attachment: Portfile added

comment:1 Changed 9 years ago by ryandesign (Ryan Carsten Schmidt)

Owner: changed from macports-tickets@… to ryandesign@…
Status: newassigned

Thanks.

comment:2 Changed 9 years ago by ryandesign (Ryan Carsten Schmidt)

Resolution: fixed
Status: assignedclosed

Committed in r128018 with these changes:

  • improved livecheck to return the actual new version
  • used extract.mkdir yes instead of worksrcpath .
  • set supported_archs i386 because what we're installing is a pre-compiled i386 binary
  • set dist_subdir ${name}/${version} because this is an unversioned distfile
  • rearranged and reformatted portfile slightly

This project is supposed to be open source, so if we could build from source instead of installing a pre-compiled binary, that would be preferable.

comment:3 Changed 9 years ago by rockettj@…

I would prefer that as well, but it's not simple. I'm working on another local branch to attempt it. The chromedriver code is embedded within the Chromium source tree, so I have to pull the entire Chromium tree and their build tools. I tried pulling their tree today and it took about 20 minutes to pull without any history over a fast connection. I'll see what I can do on that. Thanks for taking my submission.

comment:4 Changed 9 years ago by ryandesign (Ryan Carsten Schmidt)

Indeed that doesn't sound optimal. You should contact the developers of chromedriver and see if they would be willing to provide a standalone source tarball of it.

Note: See TracTickets for help on using tickets.