Changes between Version 1 and Version 2 of SummerOfCode2014_pypi2port


Ignore:
Timestamp:
Aug 16, 2014, 6:39:03 AM (10 years ago)
Author:
gaurav@…
Comment:

--

Legend:

Unmodified
Added
Removed
Modified
  • SummerOfCode2014_pypi2port

    v1 v2  
    3535ToDo for week 4
    3636
    37 
    38 
    3937=== Week # 5===
    4038(16/06/2014 - 22/06/2014)
     
    4442* Test each phase of the Portfile {fetch, checksum, extract, patch, configure, build and destroot}.
    4543
     44=== Week # 6===
     45(23/06/2014 - 29/06/2014)
     46
     47*** MID-TERM EVALUATIONS ***
     48
    4649=== Week # 7===
    4750(30/06/2014 - 05/07/2014)
     51
     52ToDo for week 7
    4853
    4954I'd recommend doing destroot tests again with trace (`port -t`).
     
    5257Also, a list of ports who cannot make it to destroot should be identified for further investigation.
    5358
     59=== Week # 8===
     60(06/07/2014 - 12/07/2014)
     61
     62ToDo for week 8
     63
     64=== Week # 9===
     65(13/07/2014 - 19/07/2014)
     66
     67ToDo for week 9
     68
     69=== Week # 10===
     70(20/07/2014 - 26/07/2014)
     71
     72ToDo for week 10
     73
     74=== Week # 11===
     75(27/07/2014 - 02/08/2014)
     76
     77ToDo for week 11
     78
     79=== Week # 12===
     80(03/08/2014 - 09/08/2014)
     81
     82ToDo for week 12
     83
     84=== Week # 13===
     85(10/08/2014 - 16/08/2014)
     86
     87ToDo for week 13
     88
    5489=== Note===
    5590* 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.