Created attachment 212610 [details]
Micropolis is a game very similar to the classic SimCity.
Thanks for submitting, it looks good and builds fine.
Do we really need -fbsd suffix when this lands in FreeBSD ports tree?
(In reply to Li-Wen Hsu from comment #1)
Well, my reasoning was that the repository I used for upstream states that it is specifically ported to FreeBSD: https://github.com/interkosmos/micropolis
So, do you think this needs a suffix or not? I'm not entirely sure about precise rules here.
(In reply to Felix Palmen from comment #2)
I don't think there is a strict rule here, but since that repository contains the patches that you created for porting https://github.com/SimHacker/micropolis to FreeBSD, it sounds a port with "external patches" of the same software. So I suggest let's keep the original name and I encourage you try to upstream patches to let them officially support FreeBSD.
(In reply to Li-Wen Hsu from comment #3)
That's a misunderstanding, the upstream repository isn't mine. And, both repositories seem pretty inactive for a long time.
Elaborating on this a bit:
https://github.com/SimHacker/micropolis which is given as the "source" seems to have different implementations, Python, C#, Java, ... there's also some TCL code there, but from what you find in the README, it seems that was abandoned earlier.
https://github.com/interkosmos/micropolis just states it's ported to FreeBSD. It's TCL/Tk (with a bundled runtime) exclusively. So, I'm not even sure this is a "fork", it might have imported some older code. According to my testing, the game works and is playable :)
The reason I added the -fbsd suffix was to make it obvious this is not the "original" micropolis but the "ported" one from this interkosmos repo. Again, I'm not sure this is the correct usage for name suffixes, so if there are good reasons not to do it, I'm fine with it as well.
Given both repositories haven't been active for a long time, I'd expect this to be a port that could live as long as you can make it compile and run correctly. Depending only on some X11 libraries, it's IMHO unlikely to break too soon. Of course, I'd also understand if you don't want to have such inactive stuff in the ports tree.
If someone is thinking about committing this, I could give it a few "testport" runs on a recent ports tree again, also with an up-to-date -CURRENT.