To comment on the following update, log in, then open the issue:
http://www.openoffice.org/issues/show_bug.cgi?id=54242
User dmores changed the following:
What |Old value |New value
================================================================================
Status|CLOSED |UNCONFIRMED
--------------------------------------------------------------------------------
Resolution|INVALID |
--------------------------------------------------------------------------------
------- Additional comments from [EMAIL PROTECTED] Tue Sep 13 09:00:10 -0700
2005 -------
Try these points:
1. The install must be done by root (Solaris pkgadd installer). Our policy for
third party applications is to not allow them to be installed by root. There are
just too many issues (security and otherwise) to deal with.
2. Install by root represents a security risk in our opinion. Why should we
allow install by root when OO is just a non-privileged application that should
not need such priv's for installation. A writeable directory and sufficient
space should be sufficient.
3. We cannot direct the install to a location of our choosing. Hardwiring the
install location is a very bad idea in my opinion. There may not be enough
space in /opt - which would create an unnecessary difficulty.
4. The application install technician may not be allowed unrestricted root
priv's in our shop/enterprise environment.
5. Native installers typically want to register all the packages and files
loaded in a system area which would not be appropriate for an install that is
intended to be served from a common network file server.
6. Use of native installers may not allow installation on one platform for use
on another platform - e.g. install Linux version from Solaris. Coping files
from the install media to an installation tree should not be platform dependent.
7. Requiring root to install OO will prevent an unprivileged user from
installing a private copy. You should not be making the assumption that this
should not be allowed - i.e. typically /opt is writable only by root.
8. OO may be relocatable, but why should I jump hoops just to accomodate
limitations in a local installer?
9. The old installer would be prefered in a heart beat over use of native
installers you have deployed here. Afterall, native installers, as I see them,
were primarilly intended to support packages for the OS and local hosting - not
network serving.
Please consider the above points. OO is an application I would like to find as
enjoyable to install for network serving as well as to use for my office
activities. Up to now, this has been the case; can you continue that?
---------------------------------------------------------------------
Please do not reply to this automatically generated notification from
Issue Tracker. Please log onto the website and enter your comments.
http://qa.openoffice.org/issue_handling/project_issues.html#notification
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
