Changes between Version 76 and Version 77 of SummerOfCode

Timestamp:

Feb 16, 2009, 4:02:29 PM (16 years ago)

Author:

raimue (Rainer Müller)

Comment:

Reordering tasks

SummerOfCode

@@ -57 +57 @@
 Potential mentors: jberry
 
+==== Logging ====
+
+Currently MacPorts has no notion of logging of build activities of a given port or sets of ports. When a a build is attempted but an error keeps it from completing, there's no way to track the problem other than the build progress that was output to the terminal, if verbose mode was requested in the first place. Otherwise, the build environment has to be pruned and the build attempted once again to even get a look at the precise error message. This is particularly problematic when automated builds are attempted, since there's usually no one around to have a look at the failure spew. An infrastructure to remedy this situation and endow MacPorts with a rich set of logging capabilities has to be developed to open up the door to true automated build runs of large sets of ports and thus to packaging of binaries, since with logging we'd have a fully reliable way of catching, reporting and processing of all sorts of fetch/configure/build/destroot/install/etc errors.
+
+This could be extended with the interaction with a server side application like MPWA that could consume these logs (read MPWA proposal). A more detailed draft of this task can be found on the LoggingProposal page.
+
+Classification: medium task to relatively challenging[[BR]]
+Programming languages: Tcl and C
+Potential mentor: jmpp, wms
+
 ==== Python Group ====
 
-Improve Python [source:trunk/base/src/port1.0/resources/group group] code.[[BR]]
+Improve Python [source:trunk/dports/_resources/port1.0/group group] code.[[BR]]
 We currently have a lot of Python modules, which are built for Python 2.4. We now need a system to re-use port information about one python port to create Ports for Python 2.4 AND Python 2.5 (and also for the upcoming 2.6 and 3.0 release).
 This though has to be made modular, so we can just re-use the description, etc. (if different versions of one module are required for different Python versions) or just re-use the whole information (checksums, etc.).
@@ -126 +136 @@
 Potential mentor: wms
 
-==== Logging ====
-
-Currently MacPorts has no notion of logging of build activities of a given port or sets of ports. When a a build is attempted but an error keeps it from completing, there's no way to track the problem other than the build progress that was output to the terminal, if verbose mode was requested in the first place. Otherwise, the build environment has to be pruned and the build attempted once again to even get a look at the precise error message. This is particularly problematic when automated builds are attempted, since there's usually no one around to have a look at the failure spew. An infrastructure to remedy this situation and endow MacPorts with a rich set of logging capabilities has to be developed to open up the door to true automated build runs of large sets of ports and thus to packaging of binaries, since with logging we'd have a fully reliable way of catching, reporting and processing of all sorts of fetch/configure/build/destroot/install/etc errors, possibly through the interaction with a server side application like MPWA that could consume these logs (read MPWA proposal). A more detailed draft of this task can be found on the LoggingProposal page.
-
-Classification: medium task to relatively challenging[[BR]]
-Prohramming languages: xml or yaml or html, C, Tcl, PHP or RoR[[BR]]
-Potential mentor: jmpp, wms
-
 ==== MacPorts Web Application ====