Changes between Version 263 and Version 264 of SummerOfCode


Ignore:
Timestamp:
May 19, 2015, 12:13:08 AM (10 years ago)
Author:
ryandesign (Ryan Carsten Schmidt)
Comment:

use TracLinks

Legend:

Unmodified
Added
Removed
Modified

  • SummerOfCode

    v263 v264  
    177177 - Installing plists in ~/Library for non-root installs if the user wants
    178178 - only modify specific XML tags to avoid clobbering additions by user
    179  - Support startupitems in standalone binary packages (currently a brutal hack is used to include daemondo in such packages, see https://trac.macports.org/ticket/43648)
     179 - Support startupitems in standalone binary packages (currently a brutal hack is used to include daemondo in such packages, see #43648)
    180180
    181181* Difficulty: Easy
    … …  
    221221Enhance the launching of GUI apps packaged by MacPorts:
    222222
    223  - Fix app icon bouncing on Dock after app launched (https://trac.macports.org/ticket/40110)
    224  - Support multiple apps per port (https://trac.macports.org/ticket/41681)
     223 - Fix app icon bouncing on Dock after app launched (#40110)
     224 - Support multiple apps per port (#41681)
    225225
    226226* Difficulty: Easy
    … …  
    238238Some mistakes are very common on newly written ports, mostly because build systems do not always respect the usual conventions. While the port works for the initial port author, it may fail for others due to these mistakes. These could be checked for automatically to catch them before adding the port to the ports tree.
    239239
    240 First, a set of tests could be run on the extracted, patched (and configured) sources. For example, a possible check could include whether the given Makefile respects the CC/CPPFLAGS/CFLAGS/LDFLAGS environment variables, which is one of the most common mistakes. Often smaller projects just [https://trac.macports.org/wiki/UsingTheRightCompiler hardcode the compiler] to `cc` or even `gcc`. This could be checked for in various ways. One option would be to overwrite Makefiles rules to verify the passed parameters. Another option would be to use a custom compiler script as `CC` that checks the flags in question are always passed to the compiler by the build system and match those given in the Portfile (or the defaults). Other binaries such as `cc`/`gcc` need to be shadowed and invocation must raise an error.
     240First, a set of tests could be run on the extracted, patched (and configured) sources. For example, a possible check could include whether the given Makefile respects the CC/CPPFLAGS/CFLAGS/LDFLAGS environment variables, which is one of the most common mistakes. Often smaller projects just [UsingTheRightCompiler hardcode the compiler] to `cc` or even `gcc`. This could be checked for in various ways. One option would be to overwrite Makefiles rules to verify the passed parameters. Another option would be to use a custom compiler script as `CC` that checks the flags in question are always passed to the compiler by the build system and match those given in the Portfile (or the defaults). Other binaries such as `cc`/`gcc` need to be shadowed and invocation must raise an error.
    241241
    242242These checks would be included as a new option in existing commands, for example `port build --check`, or a new phase `prebuildcheck` to be run before the `build` phase. This mode could be enabled automatically with a flag in `macports.conf` for MacPorts developers.
    … …  
    314314==== MacPorts statistics ==== #mpstats
    315315
    316 Enhance collection and reporting of inventory of ports installed by participating users:
    317 https://trac.macports.org/wiki/StatisticsIdeas
     316Enhance collection and reporting of inventory of ports installed by participating users: StatisticsIdeas
    318317
    319318* Difficulty: Medium