Need a better info command - with latest stable and current installed versions - as an additional column!

Please guys - needed for the core/contrib code-update scripts.

PS. If the info command knows these things and displays them - it will help bash scripts and future php/drush versions of them.

PS2. It will be best (I suppose) if some other facility(drush func / command(unnecessary IMHO) ) gets this information and the 'info' command just harvests it.

Comments

rsvelko’s picture

rsvelko commented

Once again - I need the current and latest stable versions of core and contrib projects. I need them outputted by drush commands (possibly with the -p or -b switches)

moshe weitzman’s picture

moshe weitzman commented

What would be best way to present this info while in --pipe mode? maybe JSON?

I think a good approach to is to break statusmodules out of pm_module_manage()

jonhattan’s picture

jonhattan
Primary language Spanish
Location Plasencia
commented
Title: Need a better info command - with latest stable and current installed versions » Need a better pm-releases command - with latest stable and current installed versions

`drush info` is now `drush pm-releases`. There's also `drush pm-info` that has nothing with old `info`.

There're two ways of integration:

a) make `pm-releases` use `drush_get_projects()` and provide installed version.
b) make `pm-info` or `pm-list` use `pm_get_project_info()` or `pm_get_release()`.

I prefer the first one, to avoid querying update.d.o all the time.

moshe weitzman’s picture

moshe weitzman commented

a) sounds fine to me.

jonhattan’s picture

jonhattan
Primary language Spanish
Location Plasencia
commented
Status: Active » Closed (duplicate)

Let's do it in #442088: Indicate Recommended/Supported/Development Releases in `pm-releases` Output.