| 3 | | * avoid activating the port and its dependencies if the port was already installed (and is only deactivated), just continue from the upload step |
| 4 | | * create "fail cache" and don't build the port if it hasn't been changed and is known to fail; don't even install any dependency if one of the dependencies is know to fail and hasn't been modified since (the email about build failure should still be sent though) |
| | 3 | * (DONE, [changeset:62834a4212c5b1c59df22221d896cb2c4aab3b44/mpbb 62834a42]) ~~avoid activating the port and its dependencies if the port was already installed (and is only deactivated),~~ |
| | 4 | * but continue from the upload step (partially addressed by [changeset:4162046ce0f29867d71cca6778d65dbb39b37d05/mpbb 4162046c], still a problem for `wine`) |
| | 5 | * ~~create "fail cache" and don't build the port if it hasn't been changed and is known to fail; don't even install any dependency if one of the dependencies is know to fail and hasn't been modified since (the email about build failure should still be sent though)~~ |
| 6 | | * |
| 7 | | * on top of the `portlist` (`portname`) variable, introduce a new variable that holds variants (say `+quartz -x11`) and allow building the port with those variants (the idea is not to come up with a complete list of useful builds, but to set the necessary building blocks to allow building quartz variants of ports or maybe other tricks that might occasionally be needed); see also #35897 |
| 8 | | * |
| 9 | | * |
| 10 | | * |
| 11 | | * |
| | 7 | * (see see #53976) provide means to build just a single port without any subports (for example, allow building just `wxWidgets-3.0` without `wxgtk-3.0` and others) |
| | 8 | * (see #35897, #52742) on top of the `portlist` (`portname`) variable, introduce a new variable that holds variants (say `+quartz -x11`) and allow building the port with those variants (the idea is not to come up with a complete list of useful builds, but to set the necessary building blocks to allow building quartz variants of ports or maybe other tricks that might occasionally be needed) |
| | 9 | * (see #53977) add a new variable to allow running the tests (we could later try to enable that by default for perl modules for example) |
| | 10 | * (see #52766) triggering the individual builds on the builder is currently in random order (not sure if this is possible to fix) |
| | 11 | * (see #53978) provide a variable to allow rebuilding all the ports committed between two commit numbers (useful to overcome problems due to temporary broken dependencies or broken build slaves); currently this is only possible for a single commit |
| | 12 | * (see #53979) Would it make any sense to merge portwatcher requests or rather not? The slight optimization might reduce the need to rebuild ports with several commits one after the other. |
