Hi Robert André
That's an interesting request
I guess you can't figure if the example is for building binaries or Go libs,
because there is no hard frontier between both cases in the proposed guidelines
In Go, everything is effectively a code library that can be reused elsewhere.
So the approach taken in the proposed guidelines, is that everything is a code
library, some of which happen to build binaries, or setup compatibility
symlinks, or need bootstrapping
It's a bit of a Lego guideline, you assemble the spec blocs you need, and
ignore those you don't need. The example was chosen to include as many blocks
as possible, with the walkthrough explaining their respective functions. All
the blocks are very short and succinct, don't search for long runs of shell
code like in the old guidelines
--
Envoyé de mon appareil Android avec Courriel K-9 Mail. Veuillez excuser ma
brièveté.
_______________________________________________
golang mailing list -- golang@lists.fedoraproject.org
To unsubscribe send an email to golang-le...@lists.fedoraproject.org
