Ullaakut
commented
6 years ago Hi @necrose99!
Thanks for using cameradar 😉
See the documentation on dependency management.
Cameradar currently uses dep and not glide, because glide's documentation actually recommends using dep instead:
If you have an issue with dep, let me know.
Also, please note that cameradar has been made to be used in Docker containers, so you don't need to install any dependencies on your machine and you can use the docker image instead.
necrose99
https://paste.pound-python.org/show/LMibpOgp11ESZlZ6sPbq/ glide up ... gets most deps.. gox .. for crosscompiles..
glide will try to get bin deps also.. gpo.zugaina.org/dev-go/dep , dev-go/glide Gentoo
point being for Easy ebuild mainitinace for cameradar for me also easier building for most people.. ie make a golang ebuild > @pentoo overlay so uses can build on Gentoo...
go or rust is nice since i've been porting to Arm64.. ( cd app-exploits/cameradar ebuild cameradar-1.0.ebuild (or current ver) package...) gentoo tbz2 , ebuild cameradar-1.0.ebuild rpm is a little know option /var/tmp/portage/app-exploits/cameradar..../tmp .... rpm and rpm spec.. just take note of build log.
emerge -av app-exploits/cameradar for rest of us...
glide cw [INFO] Unable to find a glide.yaml file. Would you like to create one now? Yes (Y) or No (N) y [INFO] Generating a YAML configuration file and guessing the dependencies [INFO] Attempting to import from other package managers (use --skip-import to skip) [INFO] Scanning code to look for dependencies [INFO] --> Found reference to github.com/Ullaakut/cameradar [INFO] --> Found reference to github.com/andelf/go-curl [INFO] --> Found reference to github.com/fatih/color [INFO] --> Found reference to github.com/gernest/wow [INFO] --> Adding sub-package spin to github.com/gernest/wow [INFO] --> Found reference to github.com/pkg/errors [INFO] --> Found reference to github.com/spf13/pflag [INFO] --> Found reference to github.com/spf13/viper [INFO] --> Found reference to gopkg.in/go-playground/validator.v9 [INFO] --> Found test reference to github.com/stretchr/testify/assert [INFO] --> Adding test sub-package mock to github.com/stretchr/testify [INFO] Looking for dependencies to make suggestions on [INFO] --> Scanning for dependencies not using version ranges [INFO] --> Scanning for dependencies using commit ids [INFO] Gathering information on each dependency [INFO] --> This may take a moment. Especially on a codebase with many dependencies [INFO] --> Gathering release information for dependencies [INFO] --> Looking for dependency imports where versions are commit ids [INFO] Here are some suggestions... [INFO] The package github.com/Ullaakut/cameradar appears to have Semantic Version releases (http://semver.org). [INFO] The latest release is 2.0.0. You are currently not using a release. Would you like [INFO] to use this release? Yes (Y) or No (N) y [INFO] Would you like to remember the previous decision and apply it to future [INFO] dependencies? Yes (Y) or No (N) y [INFO] Updating github.com/Ullaakut/cameradar to use the release 2.0.0 instead of no release [INFO] The package github.com/Ullaakut/cameradar appears to use semantic versions (http://semver.org). [INFO] Would you like to track the latest minor or patch releases (major.minor.patch)? [INFO] The choices are: [INFO] - Tracking minor version releases would use '>= 2.0.0, < 3.0.0' ('^2.0.0') [INFO] - Tracking patch version releases would use '>= 2.0.0, < 2.1.0' ('~2.0.0') [INFO] - Skip using ranges [INFO] For more information on Glide versions and ranges see https://glide.sh/docs/versions [INFO] Minor (M), Patch (P), or Skip Ranges (S)? m [INFO] Would you like to remember the previous decision and apply it to future [INFO] dependencies? Yes (Y) or No (N) y [INFO] Updating github.com/Ullaakut/cameradar to use the range ^2.0.0 instead of commit id 2.0.0 [INFO] Updating github.com/fatih/color to use the release v1.7.0 instead of no release [INFO] Updating github.com/fatih/color to use the range ^1.7.0 instead of commit id v1.7.0 [INFO] Updating github.com/pkg/errors to use the release v0.8.0 instead of no release [INFO] Updating github.com/pkg/errors to use the range ^0.8.0 instead of commit id v0.8.0 [INFO] Updating github.com/spf13/pflag to use the release v1.0.2 instead of no release [INFO] Updating github.com/spf13/pflag to use the range ^1.0.2 instead of commit id v1.0.2 [INFO] Updating github.com/spf13/viper to use the release v1.1.0 instead of no release [INFO] Updating github.com/spf13/viper to use the range ^1.1.0 instead of commit id v1.1.0 [INFO] Updating gopkg.in/go-playground/validator.v9 to use the release v9.21.0 instead of no release [INFO] Updating gopkg.in/go-playground/validator.v9 to use the range ^9.21.0 instead of commit id v9.21.0 [INFO] Updating github.com/stretchr/testify to use the release v1.2.2 instead of no release [INFO] Updating github.com/stretchr/testify to use the range ^1.2.2 instead of commit id v1.2.2 [INFO] Configuration changes have been made. Would you like to write these [INFO] changes to your configuration file? Yes (Y) or No (N) y [INFO] Writing updates to configuration file (glide.yaml) [INFO] You can now edit the glide.yaml file.: [INFO] --> For more information on versions and ranges see https://glide.sh/docs/versions/ [INFO] --> For details on additional metadata see https://glide.sh/docs/glide.yaml/