github.com/Ullaakut/nmap/v2/pkg/osfamilies: not found about nmap HOT 7 CLOSED

FYI, found a gentoo tool to generate the full list:
https://github.com/williamh/get-ego-vendor
The problem solve ;-)

from nmap.

If you are curious about why go modules have multiple versions, I recommend taking a look at https://blog.golang.org/using-go-modules :)

from nmap.

Also, there are different calls. The release tar.gz file has "github.com/ullaakut/cameradar" structure (low case),
however the package called "github.com/Ullaakut/cameradar"

from nmap.

Hi @blshkv !

I'm not sure what the issue is that you are pointing out by linking the go module and the import of the osfamilies package from xml.go? It is normal that there isn't a specific go module for the osfamilies package. It is a package that is part of the github.com/Ullaakut/nmap/v2, as expected.

I don't really understand why your compilation fails. On my end, running go get github.com/Ullaakut/nmap/v2/pkg/osfamilies works just fine, and so does building Cameradar both manually and in Docker.

• Which version of go are you using? Are go modules enabled?
• Did you use go get/go mod to fetch your dependencies, or did you manually download and extract the tar.gz archive? I am pretty sure that using the archive is not going to work.
• Where do you expect the package to be fetched from? Can you show me what it contains?

Removing the go module versions would be a huge breaking change and make most users upset, and creating folders named v2 and v5 would also be problematic, as it would conflict with the go module path, so it's not the right solution.

from nmap.

I'm using dev-lang/go-1.16.2, modules are enabled and manually downloaded .tar.gz. It works for any other tools just fine.
It also works fine if I create these symlinks.

Sorry, I'm not a "go" expert. I'm just trying to follow the existing Gentoo API (eclass). But I find these v2 and v5 are very confusing and not consistent with the rest of the packages.

from nmap.

Ah, so the way those versions work in modern Go (>1.13) is that there are now modules, which can be versioned, and contain one or more packages. Unfortunately, while this makes version control of multiple dependencies very neat for Go developers, it also means you can no longer just rely on the file system and use the tarballs from GitHub releases.

What you'll need to do if you want to properly download your dependencies is to run go mod download or go mod vendor.

Let me know if you need more details, but without more context on your build it's difficult to pinpoint you to the exact right direction 😅

from nmap.

There is a new 'go-modules' Gentoo eclass, but the list of dependencies is much longer.
Some modules need to have multiple versions for no real reason. This is crazy.

Ok, nevermind. I'll just symlink whatever I need ;-)

from nmap.