Changes between Version 221 and Version 222 of SummerOfCode


Ignore:
Timestamp:
Feb 3, 2014, 10:14:55 PM (10 years ago)
Author:
neverpanic (Clemens Lang)
Comment:

reflow, move ticket link

Legend:

Unmodified
Added
Removed
Modified

  • SummerOfCode

    v221 v222  
    8080== Tasks ==
    8181
    82 This is a list of some potential tasks that student GSoC members could
    83 undertake. These are just ideas, and while they express our current
    84 concerns, we are open to blue-sky projects related to MacPorts.
    85 
    86 Please note that this list is absolutely '''not exclusive'''! If you
    87 have any idea about what you want to see improved in MacPorts, you are
    88 free to propose this as your own project. In any case, we recommend you
    89 talk to mentors before writing your application.
     82This is a list of some potential tasks that student GSoC members could undertake. These are just ideas, and while they express our current concerns, we are open to blue-sky projects related to MacPorts.
     83
     84Please note that this list is absolutely '''not exclusive'''! If you have any idea about what you want to see improved in MacPorts, you are free to propose this as your own project. In any case, we recommend you talk to mentors before writing your application.
    9085
    9186=== Core tasks ===
    … …  
    9388==== Dependency calculation using SAT solving ==== #dependencies
    9489
    95 This task consists of implementing a new dependency engine for MacPorts. The current dependency engine works for everyday use, but it could be extended to support a number of features we would like to have, such as [[ticket:126|dependencies on variants]], versioned dependencies, pre-computing a plan of action (and asking the user for confirmation), conflict resolution proposals and metapackages. Note that we don't expect you to accomplish all of these ideas in one GSoC – setting the base would already be a huge help.
     90This task consists of implementing a new dependency engine for MacPorts. The current dependency engine works for everyday use, but it could be extended to support a number of features we would like to have, such as dependencies on variants (ticket:126), versioned dependencies, pre-computing a plan of action (and asking the user for confirmation), conflict resolution proposals and metapackages. Note that we don't expect you to accomplish all of these ideas in one GSoC – setting the base would already be a huge help.
    9691
    9792This task requires understanding the dependency relations (required for fetching, building, configuring; static and dynamic linking; dependence at runtime).