DebianThis forum is for the discussion of Debian Linux.
Notices
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
A .deb package is usually meant to install (binary) files into the system. A .sh (shell script) file on the other hand is meant to run some commands, rather than copy files that are inside the file (.sh includes script/text, .deb files).
Is the googleearth's .sh file really a shell script, or is it somekind of an installation binary that "extracts" itself and then builds a .deb file so the package is easier to manage in a Debian system? I don't know since I haven't got Google Earth for Linux but if you have a shell script (that runs commands), it's difficult to believe one would just create a .deb file out of it (so the deb file would simply run some existing commands rather than copy files from inside the package file).
Maybe you need to look for how Debian package files are created, from the Google. I bet there is information around.
In sid you now have the googleearth-package to convert the .bin to a .deb.....nice to hear, how does it work (haven't looked at it yet but like to give googleearth a go)
That script is in the AMD64 Sid and Etch repos as well, but it won't build a 64-bit working installation. I didn't have any trouble with the 32-bit version just installing the Google .bin file and executing it.
On my 64-bit system, tho, neither the Google .bin file nor the .deb package created from it work.
Look into the checkinstall program. The actions of the installer are made into a package and installed as that package. It supports .rpm, .deb, and .tgz.
Real Debian users don't use checkinstall, (or alien, or anything else that makes a fake .deb package). I don't think it's even in the Debian repos anymore.
Anyway. It can't change a 32-bit app into a 64-bit one.
Real Debian users don't use checkinstall, (or alien, or anything else that makes a fake .deb package). I don't think it's even in the Debian repos anymore.
Eh... I use checkinstall occasionally and the last I heard, I was a real (not fake) human being who uses Debian.
Have I now become a fake Debian user by any chance?
Well, the Debian folks decided it was just too buggy and unsafe to keep in the repos. You, as a part-time Slack user, are qualified to use it, but you're also qualified to build your own .deb packages which would be a better idea.
I used checkinstall only once to install "pentagram" which is an Ultima VIII engine for Linux. I had to compile it and did the install using checkinstall.
I don't like using checkinstall either, but it sure beats using make install.
as for creating genuine debs, I'd be glad to learn now. Off to google
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.