Rory Finnegan

I think not having an inner constructor would be the least intrusive option.

Not sure, but I'm also not really using this package anymore since Pkg.jl is sufficient now.

Can you post full output of `versioninfo(true)` and `Pkg.add("Playground")`?

Hmmm, that's failing on `chmod(join(build_dir, "playground"), "+x")`. Maybe this is an issue with FilePaths.jl? Could you try creating a file in that directory and making it executable? ``` julia> using...

Yep, looks like this might be a libc compatibility issue :( Can you post your linux distro info and the output of `ldd --version`?

> I thought Pkg3 subsumed the functionality of Playground. Is that right? For most people that's true. Technically, they're performing program isolation at different levels, so both have there place...

My guess is that `BuildExecutable` is compiling in the home directory [here](https://github.com/rofinn/Playground.jl/blob/master/src/config.jl#L103). I'm not really sure what the best work around will be, but my suggestion for now is to...

Yeah, I do this enough that I've just added the following to my juliarc. ```julia using FilePaths function Base.Pkg.add(path::AbstractPath) extension(path) == "jl" || throw(ArgumentError("Expected pkg directory to end with '.jl'"))...

FWIW, I like Package.toml (or Pkg.toml) as: 1) Config seems generic enough to be confused with a settings file that contains constants for the package/application/project code. 2) Pkg.toml leaves room...

Should we try and get this working so we can backport it to DataFrames.jl? I'm guessing @quinnj is pretty busy right now, but I'm not sure what the protocol is...