Re: Gnome 2 Install. No luck in any way

On Thu, 2002-09-26 at 18:19, dballester kernpharma com wrote:
> Hi again:
>      Two weeks trying to install gnome 2.0.2 :(. Day by day, hour by hour I
> had tried to create srpms from tar.gz with no luck ( I prefer to have a
> consistent database about software installed in my system but...sigh),
> after i tried to use Garnome, with no luck too ( gnome-vfs needs libbz2 to
> compile, and no info in the web about what rpm can have this libs, only one
> note about Conectiva distro ).
>      Anybody can point me to the right direction? Having Suse and mandrake
> srpms pointed in the gnome web, why RedHat aren't? Is Red Hat who must make
> them, or is Gnome, or are contributors?
> As Always, a lot of TIAS from a desesperated Gnome fan ;)

If you are adventurous, you might like to try my RPM-from-tarball
building scripts (gnome-rpm-tools, or "makegnome" from

I announced these a while back under the title "a new way to mangle
your RPM database" :-) but these scripts have worked well for me.
They are under constant development (as I find new packages which
they don't handle), the present version is 1.6.5. You also need the
tarball of gnome-rpm-patches, since not all of the packages have
a working RPM spec file. Please unpack it in an empty directory and
look at the README file before plunging in, though. If it doesn't
work for you, you might try changing the build order (the
gnome2modules variable in makegnome-config) to the official one
from the GNOME 2 release notes.


Hi everybody,

If the subject line hasn't scared you off, you may like to check out
my Gnome 2 RPM building scripts at

I guess this is still for DEVELOPERS ONLY.

Just download the Gnome source tarballs, or tarballs generated from a
CVS checkout, together with the patches on my page (some of the
RPM specfiles are absent or buggy) and start building!

Be warned that even if you set your prefix to something other
than /usr, some of your existing files may be overwritten.
There are three cases:
(1) The spec file uses the builtin macro %_prefix - this is OK,
    since the installation script for gnome-rpm-tools inserts
    a line to set this in your .rpmmacros file.
(2) The spec file is generated by ./configure from *,
    and uses prefix= prefix@ - this is OK, because makegnome
    passes your desired prefix to ./configure.
(3) Some of the spec files have prefix=/usr hardcoded. There
    may be good reason for this, but if so your existing package
    will probably be overwritten by an RPM update or a
    forced installation using --replacefiles - you have been

These caveats aside, there are good reasons to use a package
manager like RPM for your bleeding edge Gnome work - you can see
exactly what you have installed, and uninstall cleanly if (when)
you find it doesn't work.

Peter Wainwright

> Regards
> _______________________________________________
> gnome-list mailing list
> gnome-list gnome org
       Home:                           Work:
Email: prw wainpr demon co uk          peter wainwright nrpb org
Fax:   +44-870-0523185                 +44-1235-822656

[Date Prev][Date Next]   [Thread Prev][Thread Next]   [Thread Index] [Date Index] [Author Index]