[MacPorts] SummerOfCode modified

[MacPorts]

Page "SummerOfCode" was changed by larryv at macports.org
Diff URL: <https://trac.macports.org/wiki/SummerOfCode?action=diff&version=204>
Revision 204
Comment: break lines for better diffs
Changes:
-------8<------8<------8<------8<------8<------8<------8<------8<--------
Index: SummerOfCode
=========================================================================
--- SummerOfCode (version: 203)
+++ SummerOfCode (version: 204)
@@ -38,11 +38,21 @@
 For future reference you may check the [http://www.google-melange.com/ Google SoC website]. You will find more information on their page on [http://code.google.com/p/google-summer-of-code/wiki/AdviceforStudents Advice for Students].
 The official [http://www.google-melange.com/gsoc/events/google/gsoc2013 timeline] should be consulted for the other dates.
 
-There are several things to consider. We are willing to support and mentor students who want to gain an experience by working on the MacPorts Project. We have many ideas for potential internship subjects, yet we are open to anything that is both interesting and relevant to MacPorts. Motivated students do not necessarily need to know Tcl language beforehand, especially if they already know several scripting languages such as Python, Ruby, PHP or Perl.
+There are several things to consider. We are willing to support and
+mentor students who want to gain an experience by working on the
+MacPorts Project. We have many ideas for potential internship subjects,
+yet we are open to anything that is both interesting and relevant to
+MacPorts. Motivated students do not necessarily need to know Tcl
+language beforehand, especially if they already know several scripting
+languages such as Python, Ruby, PHP or Perl.
 
 === For the MacPorts Project ===
 
-The best way to apply is to first make contact with us, either by sending a mail to the MacPorts developer [http://lists.macosforge.org/mailman/listinfo/macports-dev "mailing list"], to the potential mentors listed below, or to IRC members on #macports on [http://freenode.net/ FreeNode].
+The best way to apply is to first make contact with us, either by
+sending a mail to the MacPorts developer
+[http://lists.macosforge.org/mailman/listinfo/macports-dev "mailing list"],
+to the potential mentors listed below, or to IRC members on #macports on
+[http://freenode.net/ FreeNode].
 
 What we expect from students for their applications:
 * Write your own abstract and proposal, copying text from this idea page is not enough.
@@ -67,15 +77,23 @@
 
 == Tasks ==
 
-This 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.
-
-Please 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.
+This 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.
+
+Please 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.
 
 === Core tasks ===
 
 ==== Binaries ==== #binaries
 
-MacPorts provides binaries but needs several enhancements. This task would include updating the chroot mechanism (ceased being functional with Snow Leopard) and adding support for variants. (See also [[MPAB|MacPorts AutoBuild]].)
+MacPorts provides binaries but needs several enhancements. This task
+would include updating the chroot mechanism (ceased being functional
+with Snow Leopard) and adding support for variants. (See also
+[[MPAB|MacPorts AutoBuild]].)
 
 * Difficulty: Relatively challenging to challenging
 * Languages: Tcl
@@ -83,10 +101,24 @@
 
 ==== Dependency calculation using SAT solving ==== #dependencies
 
-This task consists of implementing a new dependency engine for MacPorts. The current dependency engine properly deals with installing packages, but it does not deal satisfactorily with [[ticket:126|dependencies on variants]] and versions, uninstalling and upgrading. This task requires understanding the dependency relations (required for fetching, building, configuring; static and dynamic linking; dependence at runtime).
-
-Instead of re-inventing the wheel it might be helpful to use software available to solve the problem of dependency calculation, e.g. by implementing an interface to a [http://www.mancoosi.org/cudf/ Common Upgradeability Description Format]-based SAT solver. Such a solver could generate an execution plan we could propose to the user and finally execute when confirmed. For this task, the MacPorts concept of variants needs to be transformed into a representation the SAT solvers will be able to optimize. If time permits, rolling back on failed updates can also be implemented.
-There is also a [browser:trunk/dports/devel/libCUDF/Portfile libCUDF] port that might be helpful to look at.
+This task consists of implementing a new dependency engine for MacPorts.
+The current dependency engine properly deals with installing packages,
+but it does not deal satisfactorily with [[ticket:126|dependencies on variants]]
+and versions, uninstalling and upgrading. This task requires
+understanding the dependency relations (required for fetching, building,
+configuring; static and dynamic linking; dependence at runtime).
+
+Instead of re-inventing the wheel it might be helpful to use software
+available to solve the problem of dependency calculation, e.g. by
+implementing an interface to a
+[http://www.mancoosi.org/cudf/ Common Upgradeability Description Format]-based
+SAT solver. Such a solver could generate an execution plan we could
+propose to the user and finally execute when confirmed. For this task,
+the MacPorts concept of variants needs to be transformed into
+a representation the SAT solvers will be able to optimize. If time
+permits, rolling back on failed updates can also be implemented. There
+is also a [browser:trunk/dports/devel/libCUDF/Portfile libCUDF] port
+that might be helpful to look at.
 
 * Difficulty: Challenging
 * Languages: Tcl, C
@@ -94,7 +126,12 @@
 
 ==== Remove dependency on Xcode ==== #xcode
 
-MacPorts currently requires a full Xcode installation, even if the user only wishes to install prepackaged binaries or compile ports that do not use Xcode projects for building. This task be as simple as allowing MacPorts to install binary packages without Xcode present, or as complex as enabling MacPorts to be completely self-sufficient (not requiring Xcode or the Command Line Tools at all).
+MacPorts currently requires a full Xcode installation, even if the user
+only wishes to install prepackaged binaries or compile ports that do not
+use Xcode projects for building. This task be as simple as allowing
+MacPorts to install binary packages without Xcode present, or as complex
+as enabling MacPorts to be completely self-sufficient (not requiring
+Xcode or the Command Line Tools at all).
 
 * Difficulty: Medium to very challenging
 * Languages: Tcl, C
@@ -102,9 +139,15 @@
 
 ==== MacPorts port for self-management ==== #self-management
 
-The MacPorts port should be the source for updating a user’s MacPorts installation.
-
-Currently the MacPorts port is used to build the .dmg installer for MacPorts that is used for the initial installation of MacPorts, and port uses the “selfupdate” mechanism for maintaining the MacPorts installation. The selfupdate mechanism is (at least not documented as such) not accessible through the MacPorts API and does not use the MacPorts mechanisms for maintaining ports
+The MacPorts port should be the source for updating a user’s MacPorts
+installation.
+
+Currently the MacPorts port is used to build the .dmg installer for
+MacPorts that is used for the initial installation of MacPorts, and port
+uses the “selfupdate” mechanism for maintaining the MacPorts
+installation. The selfupdate mechanism is (at least not documented as
+such) not accessible through the MacPorts API and does not use the
+MacPorts mechanisms for maintaining ports.
 
 * Difficulty: Challenging
 * Languages: Tcl, C
@@ -112,7 +155,10 @@
 
 ==== Perl modules integration from CPAN ==== #cpan2port
 
-There has been [[browser:contrib/cpan2port|an attempt]] to write a script for automatic generation of Portfiles from CPAN. This would simplify the maintenance of Perl modules in MacPorts. Revive this project and finish the script or rewrite it.
+There has been [[browser:contrib/cpan2port|an attempt]] to write
+a script for automatic generation of Portfiles from CPAN. This would
+simplify the maintenance of Perl modules in MacPorts. Revive this
+project and finish the script or rewrite it.
 
 Resources:
 * http://www.gentoo.org/proj/en/perl/g-cpan.xml
@@ -125,11 +171,19 @@
 
 ==== Read packages from Python's PIP (pip2port) ==== #pip2port
 
-MacPorts should be able to more readily install python packages from pip. We don't want to integrate the build/installation process of PIP, simply parse information or eggs it provides for various packages. This information will then be used to generate a Portfile, akin to [[browser:contrib/cpan2port/cpan2port|cpan2port]].
-
-There may be instances where MacPorts package names don't match up with pip’s. In this case, pip should be the authority and all improperly named MacPorts packages should be replaced by a renamed copy. Verbose automation of this step, akin to the portcheckup script, is ideal.
-
-The [[browser:contrib/portfile-gen/portfile-gen|portfile generator]] might be helpful.
+MacPorts should be able to more readily install python packages from
+pip. We don't want to integrate the build/installation process of PIP,
+simply parse information or eggs it provides for various packages. This
+information will then be used to generate a Portfile, akin to
+[[browser:contrib/cpan2port/cpan2port|cpan2port]].
+
+There may be instances where MacPorts package names don't match up with
+pip’s. In this case, pip should be the authority and all improperly
+named MacPorts packages should be replaced by a renamed copy. Verbose
+automation of this step, akin to the portcheckup script, is ideal.
+
+The [[browser:contrib/portfile-gen/portfile-gen|portfile generator]]
+might be helpful.
 
 * Difficulty: Medium
 * Languages: Tcl, Python, C
@@ -137,7 +191,10 @@
 
 ==== Read packages from other various package managers ==== #foo2port
 
-As above with the pip2port proposal, except with other package managers, such as [http://opam.ocamlpro.com/ opam] for ocaml packages, [http://www.haskell.org/cabal/ cabal] for haskell, [http://luarocks.org/ luarocks] for lua, [https://npmjs.org/ npm] for node.js, and so on.
+As above with the pip2port proposal, except with other package managers,
+such as [http://opam.ocamlpro.com/ opam] for ocaml packages,
+[http://www.haskell.org/cabal/ cabal] for haskell, [http://luarocks.org/ luarocks]
+for lua, [https://npmjs.org/ npm] for node.js, and so on.
 
 * Classification: Medium
 * Languages: Tcl, C, OCaml, Haskell, Lua, Node.js, etc.
@@ -145,7 +202,11 @@
 
 ==== Increase test coverage ==== #testing
 
-MacPorts currently includes a [[source:trunk/base/tests|test framework]] to test features of the infrastructure. However, the tests do not cover all the code. This task consists of extending the test framework and could be broadened to develop a code coverage technology for MacPorts to make the infrastructure more robust to future changes.
+MacPorts currently includes a [[source:trunk/base/tests|test framework]]
+to test features of the infrastructure. However, the tests do not cover
+all the code. This task consists of extending the test framework and
+could be broadened to develop a code coverage technology for MacPorts to
+make the infrastructure more robust to future changes.
 
 * Difficulty: Relatively easy to very challenging
 * Languages: Tcl, C
@@ -153,7 +214,8 @@
 
 ==== Configuration and environment selftest ==== #envcheck
 
-Add a command to check current setup for common pitfalls (e.g. stuff in `/usr/local`), inspired by Homebrew’s `brew doctor` functionality.
+Add a command to check current setup for common pitfalls (e.g. stuff in
+`/usr/local`), inspired by Homebrew’s `brew doctor` functionality.
 
 * Difficulty: Easy
 * Languages: Tcl
@@ -161,7 +223,13 @@
 
 ==== Improve Trace mode ==== #tracemode
 
-Improve trace mode to the point where developers (and the build server) could run with it always turned on. This currently requires fixing some (minor) remaining bugs in the trace code itself, adjust the build system to always build the tracing library as universal binary and improving the Tcl backend of trace mode (e.g. by adding more features like a list of accessed files, speeding up the lookup by using better data structures).
+Improve trace mode to the point where developers (and the build server)
+could run with it always turned on. This currently requires fixing some
+(minor) remaining bugs in the trace code itself, adjust the build system
+to always build the tracing library as universal binary and improving
+the Tcl backend of trace mode (e.g. by adding more features like a list
+of accessed files, speeding up the lookup by using better data
+structures).
 
 * Difficulty: Medium to Easy
 * Programming languages: Tcl, C
@@ -169,7 +237,11 @@
 
 ==== Improve startupitem code ==== #startupitem
 
-MacPorts has the ability to automatically generate startup items for the current platform. For OS X, these are plist files for launchd which will be installed as `/Library/LaunchDaemons/org.macports.*.plist`. The current code would need a little care and could make use of options which have been added in recent releases of launchd.
+MacPorts has the ability to automatically generate startup items for the
+current platform. For OS X, these are plist files for launchd which will
+be installed as `/Library/LaunchDaemons/org.macports.*.plist`. The
+current code would need a little care and could make use of options
+which have been added in recent releases of launchd.
 
 Features that could be useful include (but are not limited to):
 * Not using daemondo if the daemon works fine under launchd without it
@@ -184,7 +256,11 @@
 
 ==== Reclaim disk space ==== #reclaim
 
-Improve `port clean` to be able to delete distfiles for a specified version, and all distfiles not needed by currently installed versions of ports. In general, add an action for reclaiming disk space, which would delete old distfiles and archives and uninstall inactive ports (and anything else that would help)
+Improve `port clean` to be able to delete distfiles for a specified
+version, and all distfiles not needed by currently installed versions of
+ports. In general, add an action for reclaiming disk space, which would
+delete old distfiles and archives and uninstall inactive ports (and
+anything else that would help).
 
 * Difficulty: Easy
 * Languages: Tcl, C
@@ -192,7 +268,11 @@
 
 ==== Parallel execution ==== #parallel
 
-When an action will run targets on multiple ports, run them in parallel when possible and sensible (requires tracking dependencies between both targets and ports and figuring out the maximum reasonable parallelism, e.g. several ports can fetch at once on a fast connection but you only want one 'make -j8' at a time)
+When an action will run targets on multiple ports, run them in parallel
+when possible and sensible (requires tracking dependencies between both
+targets and ports and figuring out the maximum reasonable parallelism,
+e.g. several ports can fetch at once on a fast connection but you only
+want one 'make -j8' at a time).
 
 * Difficulty: Very challenging
 * Languages: Tcl, C
@@ -200,7 +280,11 @@
 
 ==== Migrate muniversal into base (lipo merging) ==== #muniversal
 
-Integrate the [[source:trunk/dports/_resources/port1.0/group/muniversal-1.0.tcl|muniversal portgroup]] into base. Not just a direct copy-and-paste, but in a way that makes sense and preserves the way portfiles are expected to behave (which the current portgroup doesn't).
+Integrate the
+[[source:trunk/dports/_resources/port1.0/group/muniversal-1.0.tcl|muniversal portgroup]]
+into base. Not just a direct copy-and-paste, but in a way that makes
+sense and preserves the way portfiles are expected to behave (which the
+current portgroup doesn't).
 
 * Difficulty: Medium
 * Languages: Tcl, C
@@ -208,7 +292,9 @@
 
 ==== Improve fetching from version control ==== #fetchtypes
 
-Make cvs/svn/git/hg/bzr fetch types checkout into the distfiles dir and then export into the work dir, to [[ticket:16373|avoid having to re-fetch]] after cleaning the work dir.
+Make cvs/svn/git/hg/bzr fetch types checkout into the distfiles dir and
+then export into the work dir, to [[ticket:16373|avoid having to re-fetch]]
+after cleaning the work directory.
 
 * Difficulty: Easy
 * Languages: Tcl, C
@@ -216,11 +302,16 @@
 
 ==== Interactive port command ==== #interactive
 
-Write an interactive command-line tool that can be used instead of the non-interactive port(1). 
+Write an interactive command-line tool that can be used instead of the
+non-interactive port(1). 
 
 The current port(1) should be viewed as batch mode reading from stdin.
 
-An interactive tool would ask for user input to resolve many situations that cause port(1) to simply error out. For example, if you try to install a port and one of its dependencies conflicts with something already installed, it could ask if you want to deactivate the installed one and its dependents.
+An interactive tool would ask for user input to resolve many situations
+that cause port(1) to simply error out. For example, if you try to
+install a port and one of its dependencies conflicts with something
+already installed, it could ask if you want to deactivate the installed
+one and its dependents.
 
 * Difficulty: Medium
 * Languages: Tcl, C
@@ -231,7 +322,12 @@
 
 ==== Portfiles ==== #portfiles
 
-Sweep through all Portfiles and look for useful opportunities to add more built-in Tcl functions that make Portfiles more (usefully) terse, powerful, flexible or easier to write. I'm sure there is an entirely family of helper functions yet to be written here. This might also include porting additional packages to MacPorts and cleaning up or removing obsolete ports.
+Sweep through all Portfiles and look for useful opportunities to add
+more built-in Tcl functions that make Portfiles more (usefully) terse,
+powerful, flexible or easier to write. I'm sure there is an entirely
+family of helper functions yet to be written here. This might also
+include porting additional packages to MacPorts and cleaning up or
+removing obsolete ports.
 
 * Classification: Medium
 * Language: Tcl
@@ -239,7 +335,9 @@
 
 ==== Documentation and website ==== #docs
 
-Improve MacPorts [query:status!=closed&component=guide|server/hosting|website|wiki documentation, website and Trac system]. Note that pure documentation proposals are not allowed by Google.
+Improve MacPorts
+[query:status!=closed&component=guide|server/hosting|website|wiki documentation, website and Trac system].
+Note that pure documentation proposals are not allowed by Google.
 
 * Difficulty: Easy to difficult
 * Languages: PHP, Python
@@ -247,7 +345,12 @@
 
 ==== Shell environment ==== #shell-environment
 
-Add support for providing basic and port-provided environmental services to users in the `~/.profile`, `~/.cshrc`, and `~/.xinitrc` files, so that instead of manipulating the user's .profile to modify certain paths, the installer could append "`source /opt/local/etc/bash.rc`" to the end of a user's .profile file and that bash.rc would source all the files in `/opt/local/etc/bash.d`.
+Add support for providing basic and port-provided environmental services
+to users in the `~/.profile`, `~/.cshrc`, and `~/.xinitrc` files, so
+that instead of manipulating the user's .profile to modify certain
+paths, the installer could append "`source /opt/local/etc/bash.rc`" to
+the end of a user's .profile file and that bash.rc would source all the
+files in `/opt/local/etc/bash.d`.
 
 This task alone is most probably not enough for the whole Summer Of Code.
 
-------8<------8<------8<------8<------8<------8<------8<------8<--------

--
Page URL: <https://trac.macports.org/wiki/SummerOfCode>
MacPorts <http://www.macports.org/>
Ports system for OS X

This is an automated message. Someone added your email address to be
notified of changes on 'SummerOfCode' page.
If it was not you, please report to .