Hi *, On Thu, Mar 10, 2005 at 12:21:06PM +0100, Alex Thurgood wrote: > Le jeudi 10 mars 2005 � 00:49 +0100, Christian Lohmaier a �crit : > > > If you don't install your other software into custom locations, why > > would you make an exception for OOo? > > I don"t. I install all that I can into /usr/local.
You compile yourself and choose /usr/local. You are not the clueless user you are argumenting with. We talk about binary packages here. Those usually install to /usr or follow the FHS and install into /opt/<vendor/package> Again: Don't say: We need these options for the clueless user and then argument with "professional usage" The DAU fetches the rpm and installs it. Nothing more. > > > And what if one needs only *one* of those filters? > > > > You are constructing weired scenarios. Why would you only install one > > single filter? > > How many users do you know who did not install filters? (I'd love to > > hear the reasons for not installing the filters as well) > > How about because some of them require Sun's version of Java, which > isn't 'free' ? Don't install the xslt filters. Only the xslt-based filters require Java (and they don't rely on Sun's java specifically) > How about because I may not be interested in installing > PalmDoc filters, or the DocBook filter for my client who has absolutely > no use for them. Again: Then you are not the clueless user since you already know what you will/may need. > > > and in what > > > order? (And don't just say "urpmi will do that for you" because it > > > doesn't > > > always work correctly). > > > > It will. If not it is a bug. But for OOo it doesn't matter. You can > > choose whatever order you like. The dependencies are runtime > > dependencies. There are no dependencies during installation. > > I'm sorry, but that doesn't work at the moment, at least not in the beta > 2. Remember we are trying to test and foresee what kind of reaction a > user will have when he/she encounters the message : > > openofficeorg-impress requires openoffice-core-08 to be installed. > > And then the rpm install breaks off. If this is going to be fixed for > final, so that the package dependencies are automagically resolved, then > fair enough. If not, its RPM hell all over again. Read again: The dependencies are runtime dependencies. openofficeorg-impress will not work without the core packages. Thus rpm warns you and tells you what is needed. You can install openoffice-impress first and then openoffice-core, this doesn't matter. The suggested procedure is not to install each package seperately, but to extract the rpms, delete/move everything you don't want to install and then run "rpm -Uhv *.rpm" This will take care of the dependencies. > > Be fair when argumenting. All the major distribution will provide OOo > > customized/adapted for that distribution. So most of the users will use > > the OOo that came with their distribution. > > This is true and is already the case for many distributions with the > current stable versions, so why did the Community feel it had to provide > RPMs as well ? Why does OOo provide a linux-setup at all? Again: I was talking about the fact that most of the /clueless/ users you are argumenting with will not install OOo with the setup. They will have OOo preinstalled by their distribution. They will not run the old setup, nor will they install the rpms from OOo. They will update their OOo using the distribution's mechanism. RPMs are a standard. They are used widespread. RPM is recommended by the LSB. Their installation is non-interactive. Most distributions for end-users use rpm as packageformat and using rpms for OOo will register OOo within the rpmdatabase. RPMs allow the user to manage the installation the same way as every other package for the distribution. There is no need for a "setup -net" and then "setup", a common source for errors with the current setup. RPMs can easily be converted into other package formats. RPMs can easily be updated. RPMs can easily be removed. Furthermore: The rpms are generated using epm, that is an abstraction layer that allows for different package formats being created from a single configuration. The solaris packages, the rpms and the debian packages are generated this way. It is possible to plug-in other formats as well (IIRC ooobuild outputs the plain, unpacked tree (as if you would extract the rpms)) > > The large number of clueless users you're talking about will not install > > developer snapshots. They should not install the beta either. And more > > important: They probably will not need nor want to do a "custom > > install". What is needed is a more detailed description for the packages > > like "Install this package if you want to do <this and that>" to ease > > the identification of the packages. > > Agreed. But at present, how many people other than the developers > actually know what each RPM does ? I have no idea what any of the core > RPMs are for. They make up the core of OOo - they contain the things needed by every module. ciao Christian -- NP: Helloween - We Got The Right --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
