SPECS: mozilla-addon-easysearch.spec - fixed %post/%postun, rel.

[Andrzej Krzysztofowicz]

=?ISO-8859-2?Q?Pawe=B3_Go=B3aszewski?= wrote:
> On Sun, 26 Sep 2004, Andrzej Augustynowicz wrote:
> > > Author: ankry                        Date: Sun Sep 26 20:37:27 2004 GMT
> > > Module: SPECS                         Tag: HEAD
> > > ---- Log message:
> > > - fixed %post/%postun, rel. 4
> > >
> > > ---- Files affected:
> > > SPECS:
> > >    mozilla-addon-easysearch.spec (1.13 -> 1.14)
> [...]
> > > ||: +rm -f %{_libdir}/mozilla/components/{compreg,xpti}.dat \
> > > + %{_datadir}/mozilla/chrome/{chrome.rdf,overlayinfo/*/*/*.rdf} ||:
> > > +MOZILLA_FIVE_HOME=%{_libdir}/mozilla %{_bindir}/regxpcom ||:
> > > +MOZILLA_FIVE_HOME=%{_libdir}/mozilla %{_bindir}/regchrome ||:
> >     ~~~~~~~~~~~~~~~~~~~~~~~~~~
> > It isn't noarch anymore
> 
> damn right.

Right. A wrapper must be pprepared. Probably it should go to mozilla.rpm &
%{_sbindir}. Any name of the wrapper suggested ?

mozilla-chrome+xpcom-generate ?

> ankry - I think that moving to /etc can't wait until post-AC...
> 
> The best way is symlink and small trigger for that in mozilla, I think...

It's not so simple:
The generated files resides in a few directories (I know of minimum 5
files).
The dirs contain also binaries.
Mozilla might expect them to be located together.
rpm doesn't like symlinks pointing nowhere during build.
Relative symlinks from /usr/somewhere to /etc/somewhere_else are not a good
idea.
%ghost symlinks generated in some %pre scripts may be a solution.

So I prefer to solve the problems in the next step.

-- 
=======================================================================
  Andrzej M. Krzysztofowicz               ankry at mif.pg.gda.pl
  phone (48)(58) 347 14 61
Faculty of Applied Phys. & Math.,   Gdansk University of Technology