9 | | When you are done, check that haikuporter is working fine by building a simple recipe ("which" is a good choice). This will allow you to make sure everything is configured properly and working as expected. Provide a copy of the build log (haikuporter output to terminal) and/or a screenshot of the package (it is created in the packages/ folder in your haikuports directory) so we can check you completed the work. |
| 7 | Head over to the [https://github.com/haikuports/haikuports/wiki wiki on the HaikuPorts website] and go to the section ''Setting Up HaikuPorts'' and follow the instructions on how to install HaikuPorter and the HaikuPorts database. Edit your haikuports.conf file to put your username in as the packager, for email address put your username "@gci.test". |
| 8 | See the ''Tips'' section on that same wiki page to add an alias ''hp'' that saves having to type haikuporter with all its standard parameters. |
| 9 | |
| 10 | === Build a package === |
| 11 | |
| 12 | ''haikuporter --help'' shows the syntax and available parameters you need to build a package. |
| 13 | |
| 14 | Check that haikuporter is working fine by building a simple recipe ("weather" is a good choice). This will allow you to make sure everything is configured properly and working as expected. |
| 15 | |
| 16 | === What to submit at the GCI task === |
| 17 | |
| 18 | * Copy & paste the whole output when you build the package, including your haikuporter commandline, into a text file and upload it at the GCI site. |
| 19 | * Find the package you've built and double-click to open in HaikuDepot. Install it and open the application (if it's a GUI app like Weather). Take a screenshot of the whole screen and upload it at the GCI site. |
| 20 | |
| 21 | === Troubleshooting === |
| 22 | |
| 23 | If despite all efforts something just doesn't work, always copy&paste all you wrote in Terminal and what was printed back out into a textfile to upload it at the GCI site. That works much better than screenshots. |