Re: Simplifying package installation.
- From: Derek Simkowiak <dereks kd-dev com>
- To: bob cs csoft net
- cc: Justin Maurer <justin slashdot org>, Alan Cox <alan redhat com>, Miguel de Icaza <miguel gnu org>, gnome-hackers nuclecu unam mx, gnome-devel-list gnome org, recipient list not shown: ;, recipient list not shown: ;, recipient list not shown: ;
- Subject: Re: Simplifying package installation.
- Date: Thu, 26 Aug 1999 17:34:13 -0700 (PDT)
> How about this:
> Write a gnome install program.
> RPMS, DEBS, whatever is associated with it.
> When a RPM (or whatever) is opened, the install program
> first checks the package against the packaging system installed on the
> system.
> If it is not a native package, it uses alien to convert it.
> It then prompts you do you want to install it for use only on this
> account, or for use on all accounts. If you say local, it sets your rpm
> database to the one in your home and installs the rpm there. If you say
> system, it asks for the root password, and installs it via a call to rpm
> through su.
This rocks. Great idea! If none of the recognized package
systems is installed, the installer can default it to a .tar.gz and
install it wherever the user wants (and has permission to).
Programmers can distribute their software in whatever package they
prefer--RPMS, whatever. Then the installer will just convert to the
native package format of the enduser's system. We could even add features
to make Gnome installs as customizable as InstallShield installs--for
example, having a full-screen background image come up, or playing back
sounds or animations during the installation copy process. Just have a
file called "gnome-install-script" within the package's filelist.
I'm all for the above Gnome Install program. The only issues left
are the package-specific ones, i.e. user-level installs for RPM.
--Derek
[
Date Prev][
Date Next] [
Thread Prev][
Thread Next]
[
Thread Index]
[
Date Index]
[
Author Index]