rt,verror2:  verror2 to get language/programme/operation info from a context.

veyron/runtimes/google/rt/rt.go
	Store the language (from environment variables) and the
	priogramme name (from os.Argv[0]) in the runtime struct.

veyron/runtimes/google/rt/ipc.go
	NewContext() puts the language and programme name (from the runtime struct)
	into new contexts.

veyron2/rt/init.go
        Call verror2.SetDefaultContext() from rt.Init() so that when people
        pass a nil context to verror2.Make() or verror2.Convert(), they get at
        least the environment language and the programme name.  We expect the
        language to be overridden in RPC calls.

veyron2/verror2/verror.go
	Use vtrace to get the RPC name in verror2.Make and verror2.Convert().
	Remove the ContextWithOpName() call, which is no longer needed.

veyron2/verror2/verror_test.go
	Change the package clause to put the test in verror2_test.
	This was the key thing that Matt explained was needed to simplify the
	dependecy confusion I had when I tried to use vtrace before.

        This allows the mock context to be omitted (thus shortening the file),
        but requires the "verror2."  prefix to be made explicit on many
        references to verror2 symbols.  This accounts of most of the lines
        changed

Change-Id: Ibd7f109f069d5ce2ea67e966da18422bec5fb661
2 files changed
tree: 69af7cfee695030b3e687edaa90bef7e1d3efab2
  1. lib/
  2. profiles/
  3. runtimes/
  4. security/
  5. services/
  6. tools/