RFE: absolute paths in apkg output

I often find myself copying apkg make-archive or apkg srcpkg output (paths) to a tool running in different directory, making the process painful.

It would be probably better if apkg outputted absolute paths by default, with an option to use relative path (current output) if it's even worth to add - maybe it's not.

added enhancement label

I think relative paths are useful when pkg/ is passed across Gitlab builds as an artifact/cache, at least I'm not 100% sure the CI jobs are guaranteed to give you the same buildroot every time.

Yeah and output is easier to read (with human eyes) with relative paths, so maybe it should stay as is with an option to use absolute paths on-demand?

Or the other way around, WDYT?

I'm not even sure it's worth the new option TBH, just thinking about this before 1.0.

Haven't needed to read apkg output, the only parsing that happens in our builds is apkg internals passing them to/from apkg's own cache. We might need the cached ones to stay relative?

Everything else "knows" the apkg structure, not sure that's the right way to go but it worked.

Thinking about this further, the current behavior is perfectly fine, just sometimes I need to pass the full path to resulting archive / srcpkg / pkg to other tools processing them and for this case I think -A, --absolute-path or similar to set apkg path printing policy to absolute for all apkg outputs is worth consideration.

Internally, nothing would change, just when printing command output, the paths would get resolved through a shared wrapper. No passing of extra parameter around as this would be apkg option, not command option.

This is more of a wishlist feature, so I'll se if I can get it done quickly when I have cycles.