On Sat, Feb 14, 2015 at 1:30 AM, Alan McKinnon alan.mckin...@gmail.com wrote:
rpms and debs are both cpio files so the easy way is to unpack them and
see what's going on:
rpm2cpio name.rpm | cpio -iv --make-directories
dpkg -x somepackage.deb ~/temp/
For deb packages, you can use binutils'
For deb packages, you can use binutils' ar; there's no need for dpkg.
(IIRC, if you use rpm2tar, you don't need rpm installed unlike
rpm2cpio, but I'm not 100% sure.)
You are right, rpm2targz doesn't require rpm to be installed. I found
I already had it installed yesterday (via libreoffice).
Bill Kenworthy billk at iinet.net.au writes:
rpm is just a wrapper around a an archive with instructions on how to
build and or install it. I have more experience with rpm's but I
believe debs are the same. Just unwrap your .rpm/.deb file of choice
and install it manually (the
Alan McKinnon alan.mckinnon at gmail.com writes:
I see you are doing more than I thought you were doing
rpms and debs are both cpio files so the easy way is to unpack them and
see what's going on:
rpm2cpio name.rpm | cpio -iv --make-directories
dpkg -x somepackage.deb ~/temp/
Neil Bothwick neil at digimed.co.uk writes:
I doubt dpkg and rpm aren't going to be much use to you, unless you
really want to run two package managers. Besides, both are not
especially useful with the front ends apt* and yum.
I'd just use those to unpackage and maybe preprocess
On 14/02/15 05:08, James wrote:
Alan McKinnon alan.mckinnon at gmail.com writes:
...
Any special reason why you don't instead download the sources and build
them yourself with PREFIX=/usr/local ?
Lots of errant codes flying everywhere so you have to pull a code audit
to see what's in
On Fri, 13 Feb 2015 21:08:55 + (UTC), James wrote:
I doubt dpkg and rpm aren't going to be much use to you, unless you
really want to run two package managers. Besides, both are not
especially useful with the front ends apt* and yum.
I'd just use those to unpackage and maybe
Alan McKinnon alan.mckinnon at gmail.com writes:
I doubt dpkg and rpm aren't going to be much use to you, unless you
really want to run two package managers. Besides, both are not
especially useful with the front ends apt* and yum.
I'd just use those to unpackage and maybe preprocess some of
On 13/02/2015 23:08, James wrote:
Alan McKinnon alan.mckinnon at gmail.com writes:
I doubt dpkg and rpm aren't going to be much use to you, unless you
really want to run two package managers. Besides, both are not
especially useful with the front ends apt* and yum.
I'd just use those to
9 matches
Mail list logo
