Pinto v0.057 stack list problem #22

Closed
holybit opened this Issue Oct 13, 2012 · 4 comments

Comments

Projects
None yet
2 participants
Collaborator

holybit commented Oct 13, 2012

Trying to list out all the packages on all the stacks fails. Both pinto -r /repos/dir list --stack @ and pinto -r /repos/dir list @ throw errors. Sorry, I zapped my .057 install in hopes of debugging the .058 one and don't have the error handy anymore.

Also, does list output indicate which stack the package is on?

Owner

thaljef commented Oct 14, 2012

On Oct 13, 2012, at 3:38 PM, Joseph Crotty wrote:

Trying to list out all the packages on all the stacks fails. Both pinto -r /repos/dir list --stack @ and pinto -r /repos/dir list @throw error

Try:

pinto -r /repos/dir list %

I changed it from @ -> % a couple releases back, because revisions look like "stack@1234" and I wanted to them to look different.

The change should be reflected in the docs, but I may have missed a few places.

-Jeff

Owner

thaljef commented Oct 14, 2012

On Oct 13, 2012, at 3:38 PM, Joseph Crotty wrote:

Also, when it does work does the output indicate which stack the package is on?

Yes, the first column should be the stack name (unless you explicitly specify a custom --format). That column is only added when listing all stacks.

-Jeff

Collaborator

holybit commented Oct 15, 2012

I don't know how listings "should" work, but I have noticed when working with stacks (e.g., a, b and c) i sometimes get confused after piping to grep about which stack I was running a listing for.

Owner

thaljef commented Oct 15, 2012

I chose not to display the stack name when listing a single stack because it would be the same on every record, so I thought it would just be noise. On the other hand, I can see how you might forget which stack you're looking at.

I will consider adding the stack name to every listing. In the meantime, you can use the --format option to customize the output to include the stack name (or anything else that you might want to see).

thaljef closed this Oct 15, 2012

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment