View Issue Details
| ID | Project | Category | View Status | Date Submitted | Last Update |
|---|---|---|---|---|---|
| 350 | WADF | CLI | public | 26 May 2010 15:25 | 24 Nov 2011 21:42 |
| Reporter | mrosenquist | Assigned To | |||
| Priority | normal | Severity | feature | Reproducibility | have not tried |
| Status | new | Resolution | open | ||
| Product Version | 0.13.5 | ||||
| Summary | 350: Have a new simple function to access a client pear install through wadf without needing to know where it is | ||||
| Description | Have a new simple script to access a client pear install through wadf without needing to know where it is Currently I have a script to access pear for a client by calling cpear cpear ------------------------------------------------ ./pear_local/pear -c ./pear_local/.pearrc $@ ------------------------------------------------ While this is spcific to my config, a generalised version could be made in wadf Would be good to call: wadf-pear list-upgrades instead of: ./pear_local/pear -c ./pear_local/.pearrc list-upgrades | ||||
| Tags | No tags attached. | ||||
| Date Modified | Username | Field | Change |
|---|---|---|---|
| 26 May 2010 15:25 | mrosenquist | New Issue | |
| 24 Nov 2011 21:42 | timj | Note Added: 422 |