@lelldorin warum nicht die sachen in lesen von haikuports.conf?
And danach weiter basteln?
Indeed i do this, see my screenshot with the entries you can do. But i want to make it editable as a GUI and not using a text editor (Why a GUI if i do the same as with the terminal). And you need to edit the config file every time you need it. I make this as fist step starting the app too.
There are apps (StyleEdit/Pe/Koder âŚ) to edit config files.
Granted, I never used the depot package for haikuporter, pulling the source from github explains all the needed steps to setup haikuporter/haikuports.
If you donât have âhaikuporterâ linked in ~/config/non-packaged/bin it wonât work anyway, donât think your current work takes that into account?
PS, still nice work and love to see progress on this! 
Just some thoughts, you have to take into account if a package is build for primary or secondary (32bit) architecture, thus declaring projectx or projectx$secondaryArchSuffix would be needed, same for REQUIRES, BUILD_REQUIRES and BUILD_PREREQUIRES (but I think that will be for later) 
I have this already
In the app or did manually?
In the app.
But i think i need to research much more before i continue this project.