Make NativeTARDistribution usable

[olpaw]

Fixes bugs/missing features that make NativeTARDistribution usable for binary deployment of non-java projects.

[dougxc]

@gilles-duboscq , can you please have a look at this

[gilles-duboscq]

maybe s/Extract/Extracting/?

[olpaw]

Fixed.

[gilles-duboscq]

So the output argument only has a meaning when the distribution comes from a BinarySuite?

This feels a bit strange, how does it work when the distribution comes from a SourceSuite?
It looks like extracting to output should be both a post-pull and post-build action.

[olpaw]

@gilles-duboscq only if the distribution is native the output argument is considered. And native distributions can only contain native projects. Here is the usecase:

"XXX_HOSTED_NATIVE" : {
  "dependencies" : ["com.oracle.xxx.native"],
  "native" : True,
  "relpath" : True,
  "output" : "clibraries",
  "os_arch" : {
    "linux" : {
      "amd64" : {
          "path" : "build/xxx-hosted-native-linux.tar",
      },
    },
    "darwin" : {
      "amd64" : {
        "path" : "build/xxx-hosted-native-darwin.tar",
      }
    },
  }
}, 

Specifying "output" : "clibraries" in the above native distribution specification ensures that after the tar-ball got pulled it will extract its contents to output (relative to the imported binary suite dir).
Specifying "relpath" : True ensures that sub-directory structures are replicated into the tar-ball on creation (e.g. libfoo.so, include/foo.h ... here it is important that we have include/foo.h in the tarball instead of foo.h (what basename would give us)).

[olpaw]

Would it help if I rename the output attr to extract?

[olpaw]

This feels a bit strange, how does it work when the distribution comes from a SourceSuite?
It looks like extracting to output should be both a post-pull and post-build action.

If you are in SourceSuite mode output has no effect. It's only relevant for the BinarySuite case to reconstruct certain folders that the suite depends on being at specific places. I thought it would be convenient for other users as well (instead of having each user reinvent the wheel with a post-pull action). BTW, how would I hook into post-pull for a given suite anyway?

[gilles-duboscq]

So the output attribute has to match exactly the output attribute of the project that was included in the tar. We could also so that automatically. However that's not completely straightforward because project data is not currently loaded for BinarySuites.
I created #88 to track that.