------- Additional Comments From [email protected] 2005-05-05 16:48 -------
> the original lsbinstall proposal did not include support for installing
> packages. lsbinstall is intended to only be used in postinstall/preremove
> scripts, not as a general purpose system administration utility.
While I don't know the internal reasoning for lsbinstall, I see two uses for it:
a) Add lines to services, "install" inet services and install fonts,
add a path to MANPATH, update ld.so.conf, and install menus
[I left intentionally out: init.d, cron and profile.d scripts]
b) Install packages
While (a) is typical for postinstall/preuninstall scripts, I think (b) has also
a right of existance: Many ISV packages (e.g. Intel's C and Fortran compiler,
but also several others) come with a tar file containing a ./install.sh script,
some RPMs and some other files. The ./install.sh scripts askes some questions
including the famous do-you-accept-the-licence one and then installs the RPMs.
If there is no LSB-defined access to package installation/removal/query, the ISV
needs fall back to nonpackage-based installations since they may not use "rpm"
(or "alian -i"/dpkg for that matter) directly.
I'm not sure whether lsbinstall needs to be the program to offer (b), but there
should be a program/script, defined by the LSB, which do so.
--
Configure bugmail: http://bugs.linuxbase.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.
lmpx.com only provides a reader for public news (NNTP) servers. It is not
affiliated with the servers or forums shown here and is not responsible for
the content of articles, which is written by their respective authors.