Which package to choose, when no debian available ?
Linux - NewbieThis Linux forum is for members that are new to Linux.
Just starting out and have a question?
If it is not in the man pages or the how-to's this is the place!
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.
Its just ... its takes an afternoon to install the entire package that way ....
Thanks for the answer though, you're most likely right that its the best solution!
Mono should be packaged in Debians apt, however I don't know which names you'd need. You can search for it. You'd have to be using unstable to get them.
Be warned. The Debian packaging of Mono is suspect, or was last time I checked. One of the Mono developers wasn't happy.
Better way. If you don't have checkinstall, get it. With checkinstall, you can invoke the program to install a tarball and create an installable binary rpm/deb/slackpack (you are prompted to choose which if you didn't edit checkinstallrc before hand). Checkinstall will put the tarball through it's paces, create and install the binary, and leave a copy of the .deb for you to archive somewhere.
The documentation is a bit short in the discussion on using a script to string commands together for checkinstall to use. Edit the README: scroll down until you find the beginning of this quote, then cut and paste.
Quote:
NOTE: If you give no arguments to checkinstall it will run a "make install". If you give arguments, the first non-option argument will be used as the install command. This is useful when the install command is not "make install" but something else like "make install_packages" or "setup" or whatever, i.e. checkinstall make install_packages checkinstall make modules_install checkinstall install.sh checkinstall setup checkinstall rpm -i my-package-1.0.i386-1.rpm
If the package you want to install has several make and install steps, you can string together several commands.
Example: chrony-1.2.0 (atomic clock synchronization)
After ./configure <options>, the commands are: make make docs make install make install-docs install-info /opt/info/chrony.info /usr/share/info (where /opt/info is the build directory I've chosen, and /usr/share/info is the system info directory where the info package will be installed). To have checkinstall perform all the steps to include in the package you want to make, you can:
cd to the source directory (in this case: cd chrony-1.2.0).
checkinstall <options> "make && make docs install install-docs install-info /opt/info/chrony.info /usr/share/info".
or
cd to the source directory (chrony-1.2.0).
You can put all the commands in a file called "install.sh", or, better yet, chronyinstall.sh, to avoid confusing it with any other 'install.sh' on your system..
Example: give it execute permissions (chmod 755 install.sh), then run it with checkinstall.
checkinstall <options> ./install.sh
Note to self: will it still work if the first line in the file is ./configure <options> ?
Response to self: Yes, it will work. Include the ./configure <options> as the first line in the install.sh file, and watch checkinstall work it's magic. If you use the --bk option with checkinstall, checkinstall will make a backup tarball of all files before changes are made. SAVE THAT TARBALL SOMEWHERE! The file will be named 'backup-(month-day-year-time)-pre-<filename>.tgz'. If you need to restore your system, you can use tar to edit that tarball to remove files belonging to <filename>, then restore the remainder.
tar -x (extract) -C (directory where the tarball resides) -f (archive name) -p (--same-permissions) -P (--absolute-paths - don't strip leading / from file names) --same-owner -v (be verbose) --ungzip (filter through gzip)
Last edited by bigrigdriver; 09-08-2004 at 08:23 AM.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.
