Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

$GS_HOME/alt_bin/stones.st :: stones: Provide information on the running and installed stones #273

Open
8 tasks
dalehenrich opened this issue Nov 20, 2019 · 0 comments
Labels
Issue_260 porting devKitCommandLine image from pharo to gemstone

Comments

@dalehenrich
Copy link
Member

dalehenrich commented Nov 20, 2019

Defer this issue until GemStone 3.5.1 is available for use as solo extent, since 3.5.1 has an option to the gslist command (used to produce running stones list) to produce output in JSON format, so need for parsing gslist output would be eliminated.

  • create basic script class
  • translate pharo help text (use devKitCommandLine <command-name> --help to see help text) into gsdevkit_launcher format
  • add symbolic link from alt_bin to tonel script class file
  • implement command functionality
  • implement Smalltalk API (some commands will be used internally by other scripts and a Smalltalk API is essential to making this possible)
  • add test
  • identify the bash scripts that use the command (grep -r devKitCommandLine)
  • edit bash scripts to call the new script
@dalehenrich dalehenrich added the Issue_260 porting devKitCommandLine image from pharo to gemstone label Nov 20, 2019
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Issue_260 porting devKitCommandLine image from pharo to gemstone
Projects
None yet
Development

No branches or pull requests

1 participant