Apache OpenOffice (AOO) Bugzilla – Full Text Issue Listing
|Summary:||.res file installation inconsistent|
|Component:||code||Assignee:||AOO issues mailing list <issues>|
|Status:||CONFIRMED ---||QA Contact:|
|Priority:||P3||CC:||ingo.schmidt-rosbiegal, issues, lohmaier, nospam4obr, stephan.bergmann.secondary|
|Issue Type:||ENHANCEMENT||Latest Confirmation in:||---|
Description rene 2006-08-08 12:54:44 UTC
$ for i in *.rpm; do echo "$i"; rpm -qpl $i | grep \.res | grep 680; done ooo-dev-base-2.0.4-180.i586.rpm /opt/ooo-dev2.0/program/resource/abp680en-US.res /opt/ooo-dev2.0/program/resource/cnr680en-US.res /opt/ooo-dev2.0/program/resource/dbp680en-US.res /opt/ooo-dev2.0/program/resource/dbu680en-US.res ooo-dev-calc-2.0.4-180.i586.rpm /opt/ooo-dev2.0/program/resource/analysis680en-US.res /opt/ooo-dev2.0/program/resource/bf_sc680en-US.res /opt/ooo-dev2.0/program/resource/date680en-US.res /opt/ooo-dev2.0/program/resource/sc680en-US.res ooo-dev-core01-2.0.4-180.i586.rpm ooo-dev-core02-2.0.4-180.i586.rpm ooo-dev-core03-2.0.4-180.i586.rpm ooo-dev-core03u-2.0.4-180.i586.rpm ooo-dev-core04-2.0.4-180.i586.rpm ooo-dev-core04u-2.0.4-180.i586.rpm /opt/ooo-dev2.0/program/libres680li.so /opt/ooo-dev2.0/program/libres680li.so.1.1 ooo-dev-core05-2.0.4-180.i586.rpm ooo-dev-core05u-2.0.4-180.i586.rpm ooo-dev-core06-2.0.4-180.i586.rpm ooo-dev-core07-2.0.4-180.i586.rpm ooo-dev-core08-2.0.4-180.i586.rpm /opt/ooo-dev2.0/program/resource/avmedia680en-US.res /opt/ooo-dev2.0/program/resource/basctl680en-US.res /opt/ooo-dev2.0/program/resource/bf_frm680en-US.res /opt/ooo-dev2.0/program/resource/bf_ofa680en-US.res /opt/ooo-dev2.0/program/resource/bf_sch680en-US.res /opt/ooo-dev2.0/program/resource/bf_sd680en-US.res /opt/ooo-dev2.0/program/resource/bf_sfx680en-US.res /opt/ooo-dev2.0/program/resource/bf_svx680en-US.res /opt/ooo-dev2.0/program/resource/bf_sw680en-US.res /opt/ooo-dev2.0/program/resource/bib680en-US.res /opt/ooo-dev2.0/program/resource/cal680en-US.res /opt/ooo-dev2.0/program/resource/dba680en-US.res /opt/ooo-dev2.0/program/resource/dbw680en-US.res /opt/ooo-dev2.0/program/resource/deployment680en-US.res /opt/ooo-dev2.0/program/resource/deploymentgui680en-US.res /opt/ooo-dev2.0/program/resource/dkt680en-US.res /opt/ooo-dev2.0/program/resource/egi680en-US.res /opt/ooo-dev2.0/program/resource/eme680en-US.res /opt/ooo-dev2.0/program/resource/epb680en-US.res /opt/ooo-dev2.0/program/resource/epg680en-US.res /opt/ooo-dev2.0/program/resource/epp680en-US.res /opt/ooo-dev2.0/program/resource/eps680en-US.res /opt/ooo-dev2.0/program/resource/ept680en-US.res /opt/ooo-dev2.0/program/resource/eur680en-US.res /opt/ooo-dev2.0/program/resource/fps_office680en-US.res /opt/ooo-dev2.0/program/resource/frm680en-US.res /opt/ooo-dev2.0/program/resource/fwe680en-US.res /opt/ooo-dev2.0/program/resource/gal680en-US.res /opt/ooo-dev2.0/program/resource/imp680en-US.res /opt/ooo-dev2.0/program/resource/ofa680en-US.res /opt/ooo-dev2.0/program/resource/ooo680en-US.res /opt/ooo-dev2.0/program/resource/pcr680en-US.res /opt/ooo-dev2.0/program/resource/pdffilter680en-US.res /opt/ooo-dev2.0/program/resource/preload680en-US.res /opt/ooo-dev2.0/program/resource/productregistration680en-US.res /opt/ooo-dev2.0/program/resource/san680en-US.res /opt/ooo-dev2.0/program/resource/sch680en-US.res /opt/ooo-dev2.0/program/resource/sd680en-US.res /opt/ooo-dev2.0/program/resource/sdbt680en-US.res /opt/ooo-dev2.0/program/resource/sfx680en-US.res /opt/ooo-dev2.0/program/resource/spa680en-US.res /opt/ooo-dev2.0/program/resource/stt680en-US.res /opt/ooo-dev2.0/program/resource/svs680en-US.res /opt/ooo-dev2.0/program/resource/svt680en-US.res /opt/ooo-dev2.0/program/resource/svx680en-US.res /opt/ooo-dev2.0/program/resource/sw680en-US.res /opt/ooo-dev2.0/program/resource/textconversiondlgs680en-US.res /opt/ooo-dev2.0/program/resource/tfu680en-US.res /opt/ooo-dev2.0/program/resource/tk680en-US.res /opt/ooo-dev2.0/program/resource/tpl680en-US.res /opt/ooo-dev2.0/program/resource/uui680en-US.res /opt/ooo-dev2.0/program/resource/vcl680en-US.res /opt/ooo-dev2.0/program/resource/wzi680en-US.res /opt/ooo-dev2.0/program/resource/xmlsec680en-US.res /opt/ooo-dev2.0/program/resource/xsltdlg680en-US.res ooo-dev-core09-2.0.4-180.i586.rpm ooo-dev-core10-2.0.4-180.i586.rpm ooo-dev-draw-2.0.4-180.i586.rpm ooo-dev-emailmerge-2.0.4-180.i586.rpm ooo-dev-gnome-integration-2.0.4-180.i586.rpm ooo-dev-graphicfilter-2.0.4-180.i586.rpm ooo-dev-impress-2.0.4-180.i586.rpm ooo-dev-javafilter-2.0.4-180.i586.rpm ooo-dev-kde-integration-2.0.4-180.i586.rpm ooo-dev-math-2.0.4-180.i586.rpm /opt/ooo-dev2.0/program/resource/bf_sm680en-US.res /opt/ooo-dev2.0/program/resource/sm680en-US.res ooo-dev-pyuno-2.0.4-180.i586.rpm ooo-dev-testtool-2.0.4-180.i586.rpm ooo-dev-writer-2.0.4-180.i586.rpm ooo-dev-xsltfilter-2.0.4-180.i586.rpm This is not consistent. Can it be made so? (Either all things where the corssponding lib is in e.g. writer into -writer, the bf stuff into -coreXY because the binfilter stuff is there too, etc or just move them all into -core08). [ This is what I will do for the 2.0.4 packages in Debian, every file will go into openoffice.org-common ]
Comment 1 Olaf Felka 2006-08-08 13:08:19 UTC
I thin that this is a question that should be discussed at firstname.lastname@example.org. I can't see a defect here.
Comment 2 rene 2006-08-08 13:19:14 UTC
reopening. We can also discuss here in this issue. And I also can make it ENCHANCEMENT if you wish, although I really thing it is a defect. It makes no sense to keep most of the res files in core and some of them in -calc. And -calc seems to have the complete set where -base only has one of the res files for base stuff. This is non-consistent packaging, I don't see what it should be for a problem to move them to -core08 (where all the other res files are) I really like people closing with WONTFIX that fast...
Comment 3 Olaf Felka 2006-08-08 13:30:32 UTC
At first: This issue has never been closed. It just got the 'resolution'. Shurely you can discuss a question in an issue. But this will lead to a pretty long issue with no oversight. We have had enough of these issue so that's why we in QA would prefer a discussion with a handsome result.
Comment 4 Olaf Felka 2006-08-09 08:13:00 UTC
added cloph to CC
Comment 5 ingo.schmidt-rosbiegal 2006-08-09 10:50:45 UTC
I agree that it would be better to have all resource files in package core-08. Nevertheless it can be dangerous now to move them from one package to another, because this could lead to update problems. Installing with "rpm -U" rpm can say that it will not install package ABC, because the file DEF is already included in another rpm.
Comment 6 rene 2006-08-09 13:36:15 UTC
is: yes. But rpm does have a option allowing to overwrite "old" files, doesn't it? Like in Debian/dpkg: "7.5.1 Overwriting files in other packages Firstly, as mentioned before, it is usually an error for a package to contain files which are on the system in another package. However, if the overwriting package declares that it Replaces the one containing the file being overwritten, then dpkg will replace the file from the old package with that from the new. The file will no longer be listed as "owned" by the old package" That would just be solved by a Replaces: openoffice.org-calc, ... at -core08. rpm must have something similar... There were already movements between packages before, how did that get done?
Comment 7 lohmaier 2006-08-09 22:25:51 UTC
> Installing with "rpm -U" rpm can say that it will not install package ABC, > because the file DEF is already included in another rpm. That is not a problem when both affected rpms are updated at the same time. Let's say you move files from the writer to the core packages. That's not a problem since it is expected that the user will update both packages (a writer package from one version will most likely not work with the core packages from another version) The only situation when the user will see a problem is when he tries to seperately update the core and the writer package (e.g. if he does a rpm -Uhv *core*rpm only) Then rpm will complain. The user either has to remove the writer rpm first (or override with --replacefiles) or update both with the same call. i.e. rpm -Uhv *core*rpm *writer*rpm will work without a problem. (Maybe this is an occasion to add versioned dependancies (i.e the writer-2.0.4 package should require "openoffice.org-core01 = 2.0.4", not only "openoffice.org-core01")
Comment 8 ingo.schmidt-rosbiegal 2006-08-11 10:03:50 UTC
But perhaps it is an advantage that we can update single packages. This could be introduced by a kind of patch mechanism. It can be, that in the future only the calc package shall be updated. Then we will not be able to do this, if there are different versions of calc rpms with different file sets. So this file shifting would destroy this possibility. And how about Solaris and the other OOo platforms? If you shift files in scp2 from one package to another, this will affect all supported platforms.
Comment 9 rene 2006-08-24 14:13:39 UTC
is: also note that your argumentation doesn't fit here anyway. Because from 2.0.3 to 2.0.4 Embedding-*.xcu moved from whatever -coreXY they were in in to -calc, -writer etc. SO there already was a move....