Roadmap

Week # 0

A few days before the actual coding period began I was still getting to know the Macports developers. Although my project needed me to create a standalone pip2port script, however, I still needed to get well acquainted with the portfile development. Clemens gave the participants a svn primer which helped me set up my branch.

Week # 1

(19/05/2014 - 25/05/2014)

ToDo for week 1

• Create functions to query and pull data from ​pypi.

A few days have gone by and we have a basic tester script which fetches data from the xmlrpc api of pypi and gives the output to stdout. There are instances where data like description and download-url is not present for packages. We are planning to file an upstream bugs for all instances of such sort.

Week # 2

(26/05/2014 - 01/06/2014)

ToDo for week 2

• Create functions that utilize pip to fetch and extract distfiles to ./sources.
• Create functions that utilize pip to pull additional data from the extract distfiles.

Week # 3

(02/06/2014 - 08/06/2014)

ToDo for week 3

• Create functions that use collected data to write a Portfile to ./python/$name_package/Portfile.
• Create functions that run port lint, fetch, checksum and extract on ./python/$name_package.

Week # 4

(09/06/2014 - 15/06/2014)

ToDo for week 4

Week # 5

(16/06/2014 - 22/06/2014)

ToDo for week 5

• Test each phase of the Portfile {fetch, checksum, extract, patch, configure, build and destroot}.

Week # 7

(30/06/2014 - 05/07/2014)

I'd recommend doing destroot tests again with trace (port -t). This will help catch unmarked dependencies that might already be available on the system.

Also, a list of ports who cannot make it to destroot should be identified for further investigation.

Note

• If we can use pip to fetch and extract the data we should probably move the portfile and port commands to after we have collect as much data as possible to be able to write the best portfile.