To comment on the following update, log in, then open the issue: http://www.openoffice.org/issues/show_bug.cgi?id=83878
------- Additional comments from [EMAIL PROTECTED] Thu Jan 24 13:30:41 +0000 2008 ------- After some thinking about this let me state my ideas again: #1. I am still convinced a feature like this must work for all platforms. That it affects Windows as well is demonstrated by StarOffice, which brings with it the SunSearchToolbar extension. As for the FAT file system, I would not stress this too much anymore. #2. If the API supports adding an unzipped extensions (that is the file URL to an directory is passed) then it would not harm to allow this in the GUI as well. As I see it this would complement this feature. This change would also need to be documented in the GUI specification. #3.The -link command line switch is not needed because the Extension Manager can distinguish an oxt from an unzipped extension. #4.I am not much of an rpm expert, but still remember that an extension could modify the content of the unzipped directory. When installed as shared, then this fails certainly. Therefore I agree, that such an extension would probably never be bundled with an office. #5. Solved for link case. In case of adding a directory which is not in the "$UNO_USER_PACKAGES_CACHE" directory, there is no need to remove something. When adding the extension (as directory) in PackageManagerImpl::addPackage one would need to: -only unzip if a file is added, do not unzip if a directory is added -the media type of the directory could be assumed as application/vnd.sun.star.package-bundle -add the complete URL to the "external" directory to the database. See ActivePackages::Data. Adding a new member to this structure would probably make it incompatible. One could maybe use the fileName to contain the URL to the directory. The code which uses the database needs to be adapted to recognize the case that the extension is in an "external" if this is important. PackageManagerImpl::removePackage probably does not need to be touched, because it just unregisters the the extension and removes the entry from the database. Also the specification and probably the help text of unopkg (--help option) need to be adapted. --------------------------------------------------------------------- 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]
