On Sat, 2013-11-23 at 09:58 +0100, Magnus Therning wrote:
> I may be missing something, but from the view of the unpacker of the
> TGZ-ball the two are equivalent, right? So why do you prefer the
> './x/...' over 'x/...'?
>
> /M
Hi,
for a pure unpack operation, is the same. My requirement aris
On Fri, Nov 22, 2013 at 03:54:38PM +0100, Tino Keitel wrote:
> Hi,
>
> for integration in an existing build infrastructure, I want to use
> cpack with the TGZ generator to create packages that have the
> current directory (./) as the first path component. The content of
> the archive would look li
Hi,
for integration in an existing build infrastructure, I want to use cpack
with the TGZ generator to create packages that have the current
directory (./) as the first path component. The content of the archive
would look like this:
$ tar tf test.tar.gz
./x/
./x/foo
cpack currently creates pack
