Bug 806691

Summary:	RFE: Relative paths in "checkout" output
Product:	[Community] PressGang CCMS	Reporter:	Joshua Wulf <jwulf>
Component:	CSProcessor	Assignee:	Lee Newson <lnewson>
Status:	CLOSED WONTFIX	QA Contact:
Severity:	unspecified	Docs Contact:
Priority:	unspecified
Version:	1.x	CC:	jwulf, lcarlon
Target Milestone:	---
Target Release:	---
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:		Doc Type:	Bug Fix
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2012-03-29 00:30:13 UTC	Type:	---
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:

Description Joshua Wulf 2012-03-26 02:07:20 UTC

When checking out a program the current output is like this:

jwulf@nitai scratch]$ csprocessor checkout 6782
CSProcessor client version: 0.22.4
Loading configuration from /home/jwulf/.config/csprocessor.ini
Connecting to Skynet server: http://skynet.usersys.redhat.com:8080/TopicIndex/

Output saved to: /home/jwulf/scratch/Hot_Rod_Book/csprocessor.cfg
Output saved to: /home/jwulf/scratch/Hot_Rod_Book/Hot_Rod_Book-post.contentspec


Given that I'm in the cwd, perhaps a more informative format might be relative pathing?

so:

Output saved to: Hot_Rod_Book/csprocessor.cfg
Output saved to: Hot_Rod_Book/Hot_Rod_Book-post.contentspec

Comment 1 Lee Newson 2012-03-26 03:00:27 UTC

If the user, uses a root directory or a different output path then relative paths are long and messy. Perhaps if you were in the directory it was trying to save to or the directory was a subdirectory, then it could be relative.

Though having the full path makes it 100% clear where the content is being saved. So to me the negatives of relatives paths far out weigh the positives.