| 6 | This talk presents the role of PortMgr, which is the steering comittee |
| 7 | of MacPorts. They are responsible for granting commit access, setting |
| 8 | general guidelines, and act as contact for our hosting providers. |
| 9 | |
| 10 | === Automating the boring tasks === |
| 11 | '''Author:''' ''Aljaž Srebrnič'' |
| 12 | |
| 13 | Let’s face it, sometimes maintaining and updating ports is a chore, and there could be quite a lot of steps involved in creating a port. In my years as a (more-or-less) active maintainer, I noticed some common patterns: sequences of actions that could be automated and I tried to minimize the user interaction. Lastly, there is support for aliases (because no one has time for ‘port livecheck’, right?) and auto-sudo: the wrapper is aware which subcommands need root and uses sudo accordingly. |
| 14 | The scripts are far from perfect, but they are in an usable state (I use them daily). |