[opensuse-factory] what's new in M3
Heya all, Last time I wrote the M2 article and we all know what happened. Yes, we did get attention. No, it wasn't very accurate - the vast majority of stuff I talked about (after diggin' through mailing lists and other places) wasn't included yet. So, I want to better my life. And need you all for that: what do I talk about? /Jos
Le mardi 03 avril 2012, à 15:07 +0200, Jos Poortvliet a écrit :
Heya all,
Last time I wrote the M2 article and we all know what happened. Yes, we did get attention. No, it wasn't very accurate - the vast majority of stuff I talked about (after diggin' through mailing lists and other places) wasn't included yet.
So, I want to better my life. And need you all for that: what do I talk about?
GNOME 3.4.0 is there, but I guess it was on your list already. A mention on the plymouth work might be nice. Maybe some quick link to the wiki page about the tmp-on-tmpfs discussion, so people are aware this is getting discussed. Cheers, Vincent -- Les gens heureux ne sont pas pressés. -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org
On Tuesday 03 Apr 2012 15:07:23 Jos Poortvliet wrote:
Heya all,
Last time I wrote the M2 article and we all know what happened. Yes, we did get attention. No, it wasn't very accurate - the vast majority of stuff I talked about (after diggin' through mailing lists and other places) wasn't included yet.
So, I want to better my life. And need you all for that: what do I talk about?
The Go programming language version 1.0 was released and we SR'd the main package to factory this week. I hope it will be included in M3 *shrug*. We don't have a wiki page for hackers using openSUSE Go package yet as we are still working on a few existing packages after the 1.0 release, but here are some general pointers to help openSUSE hackers if they want to use the Go package/language (which is simply named "go"). Getting Started --------------- Change the editor to whichever you prefer in the following (vim, kate, emacs) zypper in go go-doc go-vim Either source /etc/profile.d/go.sh or open a new terminal to import the Go env vars into your environment. Your $GOPATH will be set to $HOME/go so either override this in your profile or create the directory. Go libraries and packages installed from the openSUSE repo are installed to $GOROOT and the system bindir. Any extra packages or binaries you install using the "go" tool will be installed to $GOPATH and $GOBIN (if it's set). Currently $GOBIN for non root users defaults to $GOPATH/bin, we currently don't add that location to your $PATH so you will either have to add it in your profile or set another location for $GOBIN (such as $HOME/bin). If you are unsure of this, please see the following documentation: http://golang.org/doc/code.html#GOPATH Once you have installed the package, an excellent way to check if everything is setup OK is to install and run the Go Tour. If you have a viable Go environment the following two commands will execute without error. go get code.google.com/p/go-tour/gotour gotour When you have a working environment, the following documentation is a great resource for first time Go hackers: http://golang.org/doc/install#next For experienced C, C++ and Java hackers I also recommend the Go FAQ. http://golang.org/doc/go_faq.html Support ------- Project homepage: http://golang.org Go language community support: Mailing List: http://groups.google.com/group/golang-nuts IRC: #go-nuts on freenode Documentation ------------- The go-doc package enables the use of the Godoc reference & API documentation server. You can run the documentation server as a service, (systemctl start godoc.service, port 6060 by default) or you can manually start it, run godoc --help for arguments. The systemd service runs with search indexing enabled so you may wish to use the godoc tool in cli mode or run it manually if you are on a RAM limited system. Sorry, there are no man pages as yet (work is underway on a tool to convert existing toolchain docs to groff format) but the toolchain, command & api reference, language spec and more are all available either through the godoc tool or directly via http://golang.org The go-vim package has a plugin :Godoc which integrates with the godoc tool. Toolchain --------- You won't find the majority of the toolchain in your PATH, Go programs and source are managed by the "go" tool, see "godoc go" or "go help" for details. We use the default Go compiler/linker/packer tools, we don't currently have a gccgo offering. You can invoke these tools directly if you so wish, see "go tool", "go help tool". Packages -------- We have a number of popular/useful packages in devel:languages:go repo, I recommend installing the associated doc package for libraries as it will integrate with the local godoc API server. In addition to these you can browse the community dashboard for additional packages: http://godashboard.appspot.com/project If you find something of use that's not in devel:languages:go let us know and we'll bundle it for you, or you can use the Go packaging guide and the .spec recipe from the wiki to package it yourself, SR's welcome. http://en.opensuse.org/openSUSE:Packaging_Go Editors ------- There are syntax highlighting and editor plugins: The packages are - go-emacs, go-kate (more up to date than current kate part syntax file), go-vim. There's an up-to-date ctags package with go support in devel:languages:go repo. The "gocode" package from the same repo provides auto-complete support for vim & emacs. Note that Go embraces a universal code style, use the "go fmt" or "gofmt" tool to aid you with this. Cheers the noo, Graham -- That which can be asserted without evidence, can be dismissed without evidence. -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org
participants (3)
-
Graham Anderson
-
Jos Poortvliet
-
Vincent Untz