Re: Binary .package Why?
"Isak Savo" <[email protected]>
| Newsgroups | gmane.comp.autopackage.devel |
|---|---|
| Message-ID | <[email protected]> |
2008/1/19, Alex Lobanovsky <[email protected]>: > > When I run my .package file (command `bash test.package`) on that target > platform it says that support code should be installed "autopackage.tar.bz2" > (I don't like this at all!), then it either downloads or uses from disk and It has to install that file. It is the support code cointaining the core of autopackage. > then it says "autopackage/libexec/autosu-tui: error while > loading shared libraries: libglib-2.0.so.0: can't open shared object file: > No such file or directory" Yes, we depend on glib for the textmode client too. Glib has nothing to do with GUI [1], it is a utility library making writing complex things in c less tiresome. You need to install it on your machine, otherwise autopackage won't work. -Isak [1] Except that it also provides the base for GTK, which is a GUI toolkit. GLib itself is not GUI related though. --------------------------------------------------------------------- To unsubscribe, e-mail: autopackage-dev-unsubscribe-OfajU3CKLf1/[email protected] For additional commands, e-mail: autopackage-dev-help-OfajU3CKLf1/[email protected]