User:Renich/Go Packaging Guidelines

Description
The Go programming language is an open source project to make programmers more productive. Go is expressive, concise, clean, and efficient. Its concurrency mechanisms make it easy to write programs that get the most out of multicore and networked machines, while its novel type system enables flexible and modular program construction. Go compiles quickly to machine code yet has the convenience of garbage collection and the power of run-time reflection. It's a fast, statically typed, compiled language that feels like a dynamically typed, interpreted language.

It, also, includes a plethora of packages and related projects.

Naming
Since go is a compiler and comes with many packages (libraries); distributed independently. Packaging guidelines should be applied only to those projects that expand go's functionality. Independent standalone packages should be named applying the  NamingGuidelines.

Building
This can be done with Packaging Howto:

%global _enable_debug_package 0 %global debug_package %{nil} %global __os_install_post /usr/lib/rpm/brp-compress %{nil}

File Placement
For now and as noted here, go has no intention to satisfy the FHS or POSIX standards.

This said, it is not impossible to put the binaries and libraries where they should be:  and   accordingly.

Besides this,  needs a   directory inside the libraries dir; this is:

Documentation
No man pages are provided for  or any of it's libraries. Go has it's own documentation application called. It is used to show documentation for the libraries and packages. It can, also, generate html documentation if needed.

Websites
Oficial website: http://golang.org/

Projects: http://godashboard.appspot.com/project

Packages: http://godashboard.appspot.com/package

Communication
Mailing list: http://groups.google.com/group/golang-nuts

IRC: irc://irc.freenode.net/go-nuts

Twitter: http://twitter.com/go_nuts

Blog: http://blog.golang.org/