08:28 <Romster> i just got home, i am tired.

08:28 <Romster> i'm not sure what the differences between bsdtar and gnutar are.

08:31 <Romster> but there is another issue with that line there is nothing to catch if bsdtar fails before it goes to && the second command, there is no || error or anything after that command. i managed to have go extract bsdtar failed but it did extract some files and bsdtar errored then the second command of && bsdtar runs fine and doesn't error out. then the go port gets built, but is missing a ton of files. just like i mentioned ages ago in that now closed

08:31 <Romster> flyspray go report.

11:26 <beerman> ..it's not closed..

15:16 <jaeger> This change fixes exactly those problems, for reference

15:16 <jaeger> Maybe that line can be improved with some error checking, but I mean this --format=gnutar thing fixes the go issue

15:17 <jaeger> (and so far in my testing has not caused any others)

21:20 <jaeger> Is it too much to ask for everyone here to keep personal attacks out of IRC, flyspray, public discussions, etc.? Of course everyone has their own opinions and if port maintainers do not agree on how they want to package stuff, fine... but calling someone "the defiler", for example... that's a personal attack and adds NOTHING useful to the conversation or to CRUX.

21:30 <beerman> I like the touch of altering the port to include bash-completion while leaving out zsh files, just for the record, I am not using this port or the other one, I am just trying to make a contrib port better (as I believe in certain standards to be uphold).