RE: Metacity upgrade method - am I an idgit?

[Jez Tucker <jezt rushes co uk>]

Havoc,

That fixed my problem. Thanks.

For anyone else that is also trying to do this, I had to do the additional
change as well as those suggested below:

run the rpmbuild -ba /usr/src/redhat/SPECS/metacity.spec

check the output of the ./configure 

  You'll have to be quick to do this - it scrolls up quickly on by box.  
  (You could always download the source and do a ./configure to get the same
results)

Now edit the spec file.

Change the line: 

SHOULD_HAVE_BEEN_DEFINED=" <blah> "

to match your ./configure output.

I.E.  I changed mine to:

SHOULD_HAVE_BEEN_DEFINED="HAVE_SHAPE HAVE_SM"

Now re-run the rpmbuild -ba /usr/src/redhat/SPECS/metacity.spec and install
your new RPM.

Clean!

Jez

-----Original Message-----
From: Havoc Pennington

> It's most likely me, but I'm having a few problems upgrading metacity on
RH
> 8.0.
> 
> I'm looking for a couple of pointers (or a more experienced voice) on the
> best method for doing this.
>
>What I would do is:
>
> - get the metacity 2.4.34 SRPM from Rawhide
> - rpm -Uvh the srpm
> - rpmbuild -ba /usr/src/redhat/SPECS/metacity.spec
> - rpm -Uvh /usr/src/redhat/RPMS/i386/metacity/*
>
> It may complain about dependencies (want a newer gtk or something),
> but if metacity from tarball built on your system you should be able
> to make the RPM build by just dropping the dependencies from the
> metacity.spec file. (Remove any Requires or BuildRequires lines that
> cause problems.)

<snip>

> Havoc


Rushes Postproduction Limited, 66 Old Compton Street, London W1D 4UH
tel: (+44) 020 7437 8676 web: http://www.rushes.co.uk
The information contained in this e-mail is confidential and may be subject to legal privilege. If you are not the intended recipient, you must not use, copy, distribute or disclose the e-mail or any part of its contents or take any action in reliance on it. If you have received this e-mail in error, please e-mail the sender by replying to this message. All reasonable precautions have been taken to ensure no viruses are present in this e-mail. Rushes Postproduction Limited cannot accept responsibility for loss or damage arising from the use of this e-mail or attachments and recommend that you subject these to your virus checking procedures prior to use.