HEADS UP: GNOME 2.14 being merged into the tree

[michael johnson]

On 5/1/06, eoghan <freebsd at redry.net> wrote:
>
> michael johnson wrote:
> >
> >
> > On 5/1/06, *eoghan* <freebsd at redry.net <mailto:freebsd at redry.net>>
> wrote:
> >
> >     Vladimir Grebenschikov wrote:
> >      > В пн, 01/05/2006 в 12:20 -0400, Joe Marcus Clarke пишет:
> >      >> On Mon, 2006-05-01 at 17:15 +0200, Michael Nottebrock wrote:
> >      >>> michael johnson schrieb:
> >      >>>
> >      >>>>> ahze@ seems to have fixed the note in UPDATING for it,
> >     although I'm not
> >      >>>>> sure it's enough. At least x11/kdelibs wants mDNSResponder,
> >     and if
> >      >>>>> avahi is already installed the dependencies will be recorded
> >      >>>>> incorrectly. I've already informed kde@
> >      >>>>
> >      >>>> We're working on a fix. Either we will disable mDNSResponder
> >     in avahi
> >      >>> Yes, please.
> >      >>>
> >      >>>> or hopefully kde@ will want to use avahi's mDNSResponder.
> >      >>> This wouldn't help the people running into the CONFLICTS right
> >     now (the
> >      >>> dependencies are already registered in people's pkgdbs when
> >     they do,
> >      >>> changing the kdelibs port won't fix that). We can try to make
> >     that work
> >      >>> later.
> >      >>>
> >      >>> Also ... seriously, do you guys even check just what is
> >     depending on the
> >      >>> things you're setting CONFLICTS with? I really was not
> >     expecting to see
> >      >>> anybody pull a fam->gamin again so soon.
> >      >> We tested this change as we do all GNOME development
> >     versions.  In the
> >      >> past, GNOME/KDE conflicts were quickly brought to light by our
> >     testers.
> >      >> It seems that this time around, we did not have anyone trying
> >     GNOME 2.14
> >      >> with KDE on the same machine.  I was rather shocked myself to
> learn
> >      >> about this and the xpdf/poppler conflict so late.
> >      >
> >      > Both problems was reported before here:
> >      >
> >      >                               From:
> >      > Vladimir Grebenschikov
> >      > <vova at fbsd.ru <mailto:vova at fbsd.ru>>
> >      >                             Sender:
> >      > vova at fbsd.ru <mailto:vova at fbsd.ru>
> >      >                                 To:
> >      > Jeremy Messenger <mezz7 at cox.net <mailto:mezz7 at cox.net>>
> >      >                                 Cc:
> >      > Tuc at T-B-O-H <ml at t-b-o-h.net <mailto:ml at t-b-o-h.net>>,
> >      > freebsd-gnome at freebsd.org <mailto:freebsd-gnome at freebsd.org>
> >      >                            Subject:
> >      > Re: Suggested mod for
> >      > gnome_upgradeXXX.sh
> >      >                               Date:
> >      > Mon, 20 Mar 2006 12:50:23 +0300
> >      >
> >      >
> >      > В вс, 19/03/2006 в 11:36 -0600, Jeremy Messenger пишет:
> >      >> We will be no longer need gnome_upgradeXXX.sh in the future
> version
> >      > of
> >      >> GNOME. Bless to the ltverhack that fix libtool bug. Upgrade
> >     GNOME 2.12
> >      > to
> >      >> 2.14 (still in MC) was a lot easier than any previous version,
> which
> >      > it
> >      >> can be done with portupgrade now. About four to five steps to do
> >     it.
> >      >> Here's what I did with GNOME 2.12 to 2.14:
> >      >>
> >      >>       pkgdb -Ff (need for gst stuff)
> >      >>       portupgrade -f -o net/avahi howl-\*
> >      >>       portupgrade -a
> >      >>       portupgrade -f -o x11/gnome-screensaver
> xscreensaver-gnome-\*
> >      >>
> >      >> The steps might be change if there is any better. Like might be
> best
> >      > to
> >      >> follow UPDATING before do the portupgrade -a.
> >      >
> >      > First of all thanks for good work.
> >      >
> >      > Unfortunately, I've do this upgrade before above suggestion, so I
> was
> >      > forced to find the solution with howl -> avahi by myself.
> >      >
> >      > Also there is one more conflict of this kind:
> >      > evinice requires poppler, but poppler conflicts with already
> >     installed
> >      > xpdf:
> >      > ===>  Installing for poppler-0.5.1
> >      >
> >      > ===>  poppler-0.5.1 conflicts with installed package(s):
> >      >       xpdf-3.01_2
> >      >
> >      >       They install files into the same place.
> >      >       Please remove them first with pkg_delete(1).
> >      > *** Error code 1
> >      >
> >      > Stop in /usr/ports/graphics/poppler.
> >      > *** Error code 1
> >
> >     Regarding poppler...
> >     Is this a requirement for a successful gnome 2.14 upgrade? Mine is
> >     running at the moment, and this did fail...
> >
> >
> > if you want to use the full gnome desktop (evince), than yes. But you
> > can keep xpdf installed if you'd rather not have evince.
> >
> > Michael
>
> ok thanks
> So can i make deinstall xpdf after my portupgrade and make install for
> poppler? Should this suffice or will i need to run portupgrade again?


Just deinstall xpdf and run portupgade again, we're working on splitting
poppler up a little bit more to not conflict with xpdf. We should have it
ready sometime this evening.

Michael



Eoghan
>