let's try this again: how to update mozilla without breaking nautilus

Daniel Resare yellowdog-general@lists.terrasoftsolutions.com
Fri Jul 26 06:31:01 2002


fre 2002-07-26 klockan 14.04 skrev R Shapiro:
> Konstantin Riabitsev writes:
>  > I'm not sure what would be involved in rebuilding nautilus with the new
>  > moz. It's probably going to suck. :)
> 
> As I may have mentioned earlier, I grabbed a nautilus src rpm when I
> first ran into this problem and tried to rebuild it.  It failed at the
> very end, during the packaging phase (some files it expected to find
> weren't present). If the rebuild had succeeded I'm pretty sure this
> would have fixed the problem, just as your rebuild of galeon fixed
> that problem.  But I decided it was better to ask here before trying
> to debug the spec file myself (ugh).  Sounds like I may have to do
> that after all - either that or give up on YD's gnome build entirely
> and switch to ximian.  Or live with a nautilus that mostly works, but
> not completely.  That's beginning to sound more and more appealing :)
> 

Not finding files at the end of rpm build usually indicates that there
are missing packages on the system (usually -devel packages). When
configure is run at the beginning of rpm build it fails to detect
certain components, which in turns off some conditional builds in the
package that the spec file tries to incorporate at the end.

Ususally all packages needed to build a ceratin package are listed with
the BuildRequires header in the .spec-file, but since the build machines
on ximian/yellowdog/redhat always have a full install they often don't
see these problems.

If you want to search for the problem, you should look through the
output of the configure for a line like 'checking for XXX - version >=
0.5.1... no'. Then try to install the XXX-devel rpm and try a rebuild.

Good luck!
/noa