I have found that usually when a package fails to install like the .tgz you mentioned. The name of the tarball and the parent directory it contains are not exactly the same eg.SimplyFlower wrote:Thank you. I tried installing both a .deb and a .tgz as alien packages. With the .tgz, Pet-Get exited with errors and told me to clean-up the /root/.packages directory. With the .deb, Pet-Get reported it as installed, but it really wasn't. Oh well, I assume it probably works with some packages and not with others.
tarball = my-package.tar.gz,
parent directory =my-package-0.0.1.
The easiest way to check would probably be to untar the package in a temporary directory and compare the names here.
Code: Select all
tar xvfz my-package.tar.gz
Code: Select all
tar cvfz my-package-0.0.1.tar.gz my-package-0.0.1
If you find you cant try this from a terminal.
for .deb
Code: Select all
dpkg --install my-package.deb
What I used to do back then was create my own alien tar.gz files from them this way.
1/ Open the package
for deb
Code: Select all
undeb my-package.deb
Code: Select all
unrpm my-package.rpm
3/ move all the directories an files from the original package into the my-package directory
4/ Create a new tarball as mentioned above making sure the name of the directory and the tarball are identical.