rpm2cpio outputs to stdout, which makes it natural and efficient to use for
piping: 'rpm2cpio foo.rpm|cpio -idv'. rpm2archive however behaves very
differently by silently creating a .tgz in the current directory. This breaks
the rule of least surprise really, especially given the long-standing behavior
of rpm2cpio.
This causes head-scratching from users (me included), inefficient piping
because you then need to use 'cat foo.rpm|rpm2archive|tar x' instead of
'rpm2archive foo.rpm|tar x', and it means it cannot replace the aging rpm2cpio
which can't handle large files. Once the behavior is made close enough, we can
just 'rm rpm2cpio.c' and symlink it to rpm2archive instead.
--
Reply to this email directly or view it on GitHub:
https://github.com/rpm-software-management/rpm/issues/2208
You are receiving this because you are subscribed to this thread.
Message ID: <rpm-software-management/rpm/issues/2...@github.com>
_______________________________________________
Rpm-maint mailing list
Rpm-maint@lists.rpm.org
http://lists.rpm.org/mailman/listinfo/rpm-maint
