To comment on the following update, log in, then open the issue:
http://www.openoffice.org/issues/show_bug.cgi?id=48408
User cloph changed the following:
What |Old value |New value
================================================================================
Status|UNCONFIRMED |RESOLVED
--------------------------------------------------------------------------------
Keywords|needmoreinfo, oooqa |oooqa
--------------------------------------------------------------------------------
Resolution| |WONTFIX
--------------------------------------------------------------------------------
------- Additional comments from [EMAIL PROTECTED] Thu Jul 7 04:43:01 -0700
2005 -------
1st of all:
You can get rpm-binaries (including rpm2cpio) in tar.gz format:
ftp://ftp.rpm.org/pub/rpm/dist/rpm-4.1.x/rpm-4.1.i386.tar.gz
2nd: the only "requirement" of the packages is "/bin/sh" and that only for the
desktop-integration packages and for one of the core packages and the pyuno
package.
The core-package creates a symlink to OOo's libfreetype if the system doesn't
provide one. The pyuno package creates two symlinks within the OOo-directory.
3rd you should not blindly install every package that is included in the
tarball. If you don't run <distribution> there's little sense in installing the
openofficeorg-<distribution>-menus package.
> Trying to support the native package type for all 400+ linux distros is a
> loosing battle.
This statement is nonsense. There is either rpm or deb or <something different>.
rpms are already provided. The build-process allows the creation of debs. (see
http://ftp.linux.cz/pub/localization/OpenOffice.org/devel/680/ for debs created
by that build-process).
The <something-different> users can use rpm2cpio to extract all the files and
simply put the output-tree to a location of their liking.
> You HAD a solution that worked on every Linux I know of [...]
No, it did not work. Not when it comes to integration in the
desktop-environment. People always complained: Bah, why you're using a
proprietary installer? - now they complain "Why aren't you using a proprietary
installer".
Going back to the old installer is a wontfix. It just drags away too many
ressources from more important stuff.
> Sure, I can use a tool like that, but when helping my Realtor friend on the
> phone that is NOT going to work.
If your friend is not using a rpm or deb-based distribution he will know how to
solve this problem, otherwise he is using the wrong distribution.
Furthermore: All the main distributions provide OOo as well. You can get OOo for
gentoo using ebuild/portage, you can get OOo for deb-based systems using
apt-get, ...
High effort (not only one-time but continuous), only small gain -> wontfix.
---------------------------------------------------------------------
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]
