Mailinglist Archive: opensuse (4208 mails)

< Previous Next >
Re: [SLE] gaim-80
  • From: 404 <textbox@xxxxxxxxx>
  • Date: Mon, 26 Jul 2004 15:17:04 -0400
  • Message-id: <2b77f5ef04072612177f02954e@xxxxxxxxxxxxxx>
http://guru.unixtech.be/rpm/packages/Network/gaim/

Gaim for SuSE




On Mon, 26 Jul 2004 09:49:32 -0700, Terry E. Milnes Jr.
<neofax_99@xxxxxxxxxxx> wrote:
> On Monday 26 July 2004 02:39 am, Josephine wrote:
> > On Monday 26 July 2004 08:53, Terry E. Milnes Jr. wrote:
> > > On Sunday 25 July 2004 11:39 pm, Erik Jakobsen wrote:
> > > > Terry E. Milnes Jr. wrote:
> > > > >This rpm complains about the perllocal.pod conflicting with
> > > > > perllocal.pod in Video-DVDRip-0.50.18-0.pm.0. Any suggestions on how
> > > > > to install? Thanks!
> > > > >
> > > > >NeoFax
> > >
> > > The package will not install with those files conflicting. That is what I
> > > get when I do rpm -Uvh gaim*.i586.rpm. No, I do not want to do a
> > > --nodeps or --force install of gaim. I may just have to get the SuSE
> > > spec file and try to compile it that way. Thanks!
> > >
> > > NeoFax
> >
> > it would be much easier just to compile the sources from gaim. you just
> > need the gtk headers, pkgconfig and that would be all if i remember
> > correctly. then just a configure, make, make install and end of stress.
> >
> > Josephine
> However, this will not reflect in the rpm database. Why have a rpm
> distribution if you are just going to recompile everything from source. I
> can understand compiling from source if the distribution does not package the
> program you want to use. However, gaim is already packaged and it is just as
> easy to download the SuSE provided source package of gaim and the source of
> gaim and change the .spec file and rebuild a new rpm, thus keeping your rpm
> database fresh.
>
>
>
> NeoFax
>
> --
> Check the headers for your unsubscription address
> For additional commands send e-mail to suse-linux-e-help@xxxxxxxx
> Also check the archives at http://lists.suse.com
> Please read the FAQs: suse-linux-e-faq@xxxxxxxx
>
>

< Previous Next >
Follow Ups