search

whyrusleeping / gx

A package management tool
MIT License
1.88k stars 110 forks source link

Would be useful to list version or short version of the hash when installing #131

Closed daviddias closed 10 months ago

daviddias commented 7 years ago

To distinguish duplicates

...
installation of dep failstore complete!
installation of dep retry-datastore complete!
installation of dep failstore complete!
...
whyrusleeping commented 7 years ago

@diasdavid There is a verbose mode you can use: gx --verbose install. I'm also working on a new UI for install that will have nicer information (including the hash) by default :)

whyrusleeping commented 7 years ago

@diasdavid try building gx from latest master, let me know what you think of the install process :)

daviddias commented 7 years ago

Hit this roadblock:

» make install
go install
main.go:19:2: cannot find package "github.com/whyrusleeping/progmeter" in any of:
        /usr/local/go/src/github.com/whyrusleeping/progmeter (from $GOROOT)
        /Users/koruza/code/go-projects/src/github.com/whyrusleeping/progmeter (from $GOPATH)
make: *** [install] Error 1

Do I need to do some gx commands magic first?

Steps to reproduce:

> git clone git@github.com:whyrusleeping/gx.git
> cd gx
> make install
victorb commented 7 years ago

@diasdavid do go get -v ./... to install dependencies, then make install

daviddias commented 7 years ago

oh right. My bad, forgot about go workspaces.

daviddias commented 7 years ago

Seems that gx is printing the 'current repo version' instead of the tool itself. This got me confused: image

daviddias commented 7 years ago

Using latest gx still got me this: image

victorb commented 7 years ago

Make sure you're actually using the right gx binary, when you do gx install --help, it should list --nofancy as one of the options.

Worth to keep in mind that ipfs/go-ipfs actually pulls down its own copy of gx when you do make install, so if you use that as a testing repo, make sure to run gx install on it's own.

On Tue, Jul 4, 2017 at 12:14 PM, David Dias notifications@github.com wrote:

Using latest gx still got me this: [image: image] https://user-images.githubusercontent.com/1211152/27826157-f98daf1c-60a9-11e7-8fa2-7ffd1e884fca.png

— You are receiving this because you commented. Reply to this email directly, view it on GitHub https://github.com/whyrusleeping/gx/issues/131#issuecomment-312841075, or mute the thread https://github.com/notifications/unsubscribe-auth/AAcD9P-bX_x5kCqaJRn2RztBwG78LYvRks5sKhCVgaJpZM4NhBEn .

Kubuxu commented 7 years ago

Also install location might be different so either try reopening the shell or doing hash -r to refresh the PATH cache.

whyrusleeping commented 7 years ago

Seems that gx is printing the 'current repo version' instead of the tool itself

Huh, i guess npm version prints the version of the tool. gx should probably do the same here?

daviddias commented 7 years ago

@whyrusleeping that is what I expected.

victorb commented 7 years ago

Huh, i guess npm version prints the version of the tool. gx should probably do the same here?

Actually, npm version prints out a lot of versions, the cli version and current directories application's version included.

This is example of running npm version in ipfs/js-ipfs

{ ipfs: '0.23.1',
  npm: '5.0.0',
  ares: '1.10.1-DEV',
  http_parser: '2.7.0',
  icu: '57.1',
  modules: '48',
  node: '6.9.5',
  openssl: '1.0.2k',
  uv: '1.9.1',
  v8: '5.1.281.89',
  zlib: '1.2.8' }