I'm trying to install hamachi [1] on Debian (arm).
I want the smallest install I can get away with, but at the moment I'm getting the following dependencies: alien at autopoint bc binutils build-essential bzip2 cpp cpp-4.4 cups-bsd cups-client cups-common debhelper dpkg-dev fakeroot g++ g++-4.4 gcc gcc-4.4 gettext gettext-base git html2text intltool-debian libalgorithm-diff-perl libalgorithm-diff-xs-perl libalgorithm-merge-perl libc-dev-bin libc6-dev libcurl3-gnutls libdpkg-perl libelf1 liberror-perl libgmp3c2 liblua5.1-0 libmail-sendmail-perl libmpfr4 libnspr4-0d libnss3-1d librpm1 librpmbuild1 librpmio1 libstdc++6-4.4-dev libsys-hostname-long-perl libtimedate-perl libunistring0 linux-libc-dev lsb-core lsb-release m4 make manpages-dev ncurses-term patch pax po-debconf rpm rpm-common rpm2cpio time
It installs and runs OK but I don't want all that stuff on my box afterwards!
Seeing alien in the list makes me conclude that this is a repackaged rpm and maybe that's what's causing the problem. However if I try to "apt-get remove alien" afterwards, hamachi gets removed.
What are my options to work around this?
Unfortunately Hamachi is not free and therefore I don't have access to the source.
[1] https://secure.logmein.com/labs/
On 28 May 2012 17:05, Mark Rogers mark@quarella.co.uk wrote:
I'm trying to install hamachi [1] on Debian (arm).
It depends on a C and a C++ compiler?!?
Tim.
On 28 May 2012 17:27, Tim Green timothy.j.green@gmail.com wrote:
On 28 May 2012 17:05, Mark Rogers mark@quarella.co.uk wrote:
I'm trying to install hamachi [1] on Debian (arm).
It depends on a C and a C++ compiler?!?
I *think* it just depends on alien, which itself depends on pretty much everything else. I might be wrong though.
On the hamachi download page they also have an rpm; how (given I only have Debian-based systems) would I check what its dependencies are?
Let's say I wanted to install hamachi via the documented deb install, then backup all the relevant hamachi binaries and config, then apt-get remove hamachi and its dependencies, before restoring my backup. How would I work out which files I needed to backup?
On 29 May 2012 06:06, Mark Rogers mark@quarella.co.uk wrote:
Let's say I wanted to install hamachi via the documented deb install, then backup all the relevant hamachi binaries and config, then apt-get remove hamachi and its dependencies, before restoring my backup. How would I work out which files I needed to backup?
You can see the files in a .deb using: dpkg -c package.deb
On 28/05/12 17:05, Mark Rogers wrote:
It installs and runs OK but I don't want all that stuff on my box afterwards!
Why not download the standalone binaries in the tar file on that page and run them through ldd and find out what they really need.
If it's not issued by an apt repository there is hardly any point installing from the deb package anyway, and looking at those dependencies I am guessing it was packaged by a complete moron.
On 03/06/12 15:08, Wayne Stallwood wrote:
Why not download the standalone binaries in the tar file on that page and run them through ldd and find out what they really need.
Hmm, thanks for pointing out the obvious (well the install from binary option was obvious, even if ldd wasn't to me).
In any case, I downloaded the tarball and ran the install script in it, which wanted me to install the "lsb" package, which dragged in all those dependencies...
Looking at the script, all it needed was some helper scripts for copying scripts into the right directories and setting their permissions, and for installing an init.d script. Doing this manually without lsb was pretty trivial, although bearing in mind that I had already done the full install (then uninstall) on this system it may be that I'm missing something that was done by the original install, so I won't know for sure until I try again on a clean box.
If it's not issued by an apt repository there is hardly any point installing from the deb package anyway, and looking at those dependencies I am guessing it was packaged by a complete moron.
Looks (so far) like it was the install script not the packaging that was the issue. "lsb" is one hell of a dependency for some wrappers to "cp" and "chmod"....
On 06/06/12 09:57, Mark Rogers wrote:
Looking at the script, all it needed was some helper scripts for copying scripts into the right directories and setting their permissions, and for installing an init.d script. Doing this manually without lsb was pretty trivial, although bearing in mind that I had already done the full install (then uninstall) on this system it may be that I'm missing something that was done by the original install, so I won't know for sure until I try again on a clean box.
I've now tried it on a clean box, albeit based on an x86 chip, and a simple script to cp and chmod the files to their correct locations seems to have worked fine.
The only bit I'm unsure of is the "correct" way to install an init.d startup script; copying the file into /etc/init.d and running it works, but obviously that won't auto-start on power-up. Lurking in the back of my brain I recall using chkconfig or update-rc.d but that's not installed on my ARM (Debian 6) box, what should I use instead? Or should I just create the symlinks manually?
Mark Rogers asked:
The only bit I'm unsure of is the "correct" way to install an init.d startup script; copying the file into /etc/init.d and running it works, but obviously that won't auto-start on power-up. Lurking in the back of my brain I recall using chkconfig or update-rc.d but that's not installed on my ARM (Debian 6) box, what should I use instead? Or should I just create the symlinks manually?
update-rc.d should be installed. It's in the sysv-rc insserv or sysvinit package. It's in sbin, so not on everyone's path.
If you create the symlinks manually, nothing should break.
Hope that helps,
On 03/07/12 01:07, MJ Ray wrote:
update-rc.d should be installed. It's in the sysv-rc insserv or sysvinit package. It's in sbin, so not on everyone's path.
Sorry for the slow reply to this, only just had chance the fire the box up.
update-rc.d is in /usr/sbin (not /sbin where I was looking). But yes it is there, thanks.
-
Mark Rogers -
MJ Ray -
Tim Green -
Wayne Stallwood