qulogic commented on the pull-request: `Fix not listing packages with external tests only`
that you are following:
@obudai a lot of Go projects use internal in the package path to mean
the same thing as the internal keyword. Welcome to the wonderful land of underspecified Go
I don't understand where you get the idea that this is some sort of hack that
non-standard-library packages are taking advantage of. The use of `internal` was described
in a [design document](http://golang.org/s/go14internal)
that has been in use since Go
Therefore, to be safe, golist should filter anything with internal in
the path, unless requested explicitly with a specific switch. (and upstreams that use
internal to mean something else than internal should probably rename their Go package now
that internal as a package name has been used as internal by many Go projects)
There is no other way for `internal` to be interpreted, so I don't know what you mean
about other upstreams.
I do agree that if `golist` is specifying an internal path as something that goes in
`Provides`, then that's a bug and it should be fixed.
I know, it's clear as mud.
It is clear; you're confused.
To reply, visit the link below or just reply to this email