[MacPorts] SummerOfCode modified

MacPorts noreply at macports.org
Mon Aug 22 16:59:30 PDT 2011


Changed page "SummerOfCode" by raimue at macports.org from 188.195.200.159*
Page URL: <https://trac.macports.org/wiki/SummerOfCode>
Diff URL: <https://trac.macports.org/wiki/SummerOfCode?action=diff&version=167>
Revision 167
Comment: Completed projects moved to SummerOfCode2011

-------8<------8<------8<------8<------8<------8<------8<------8<--------
Index: SummerOfCode
=========================================================================
--- SummerOfCode (version: 166)
+++ SummerOfCode (version: 167)
@@ -86,20 +86,6 @@
 Programming languages: Tcl[[BR]] 
 Potential mentor: TBD 
 
-==== Scan for broken dynamic libraries for rebuild ==== #rev-upgrade 
-
-Upgrading any port can naturally break its dependents if using dynamic libraries. The only way to fix this is currently rebuilding all dependents, no matter if necessary or not. MacPorts should get a new command to scan installed dynamic libraries and binaries for linker errors and mark the corresponding port for rebuild. After checking all files, broken ones should get rebuild in the correct order. Probably it has to do the check again after each set of rebuilds. 
-
-{{{ 
-port rev-upgrade [portname] 
-}}} 
-
-If you are familiar with Gentoo, this would be the equivalent of the revdep-rebuild command. See #17473 for more information. 
-
-Classification: easy to medium task[[BR]] 
-Programming languages: Tcl[[BR]] 
-Potential mentor: raimue 
-
 ==== Dependencies ==== #dependencies
 
 This task consists of implementing a new dependencies engine for MacPorts. The current dependency engine properly deals with installing packages, but it does not deal satisfactorily with dependencies on variants (and versions), uninstalling and upgrading. This very challenging task requires a complete formalization of the use cases (installation, upgrade, uninstallation) and of the user needs before any implementation, as well as a deep understanding of the dependency relations (required for fetching, building, configuring; static and dynamic linking; dependence at runtime).
@@ -107,21 +93,6 @@
 Classification: very challenging task[[BR]]
 Programming languages: Tcl and C[[BR]]
 Potential mentors: TBD
-
-==== Check dependencies after destroot ==== #depcheck
-
-MacPorts currently has trace mode to check which files are accessed during build and if they are in the dependency chain. This requires injecting the tracelib in all code that is run and interception all open calls and make checks on the pathnames which slows down the procedure. This task is about creating another feature for verifying the dependencies of a build.
-
-A new phase would be created which is to be run after the destroot phase to verify files.
- * It would iterate over all binaries and dynamically linked libraries in the destroot which are going to be installed and check the recorded paths against the dependency chain.
- * It will report broken symlinks, e.g. those pointing to the destroot
-Any problems found should be reported.
-
-This would be great to do a quick check if the dependencies are met without the effort from trace mode. It could also help to identify unnecessary dependencies. If this actually runs fast enough it could as well be enabled by default, although it should only be necessary for maintainers.
-
-Classification: medium task[[BR]]
-Programming languages: Tcl and C[[BR]]
-Potential mentor: raimue
 
 ==== MacPorts Port for self-management ==== #self-management
 

-------8<------8<------8<------8<------8<------8<------8<------8<--------

* The IP shown here might not mean anything if the user or the server is
behind a proxy.

--
MacPorts <http://www.macports.org/>
Ports system for Mac OS

This is an automated message. Someone at http://www.macports.org/ added your email
address to be notified of changes on SummerOfCode. If it was not you, please
report to .


More information about the macports-changes mailing list