Gnome ports messed up (dependency loops)

[Jeremy Messenger]

On Fri, 04 Apr 2008 12:01:37 -0500, Michael Johnson <ahze at freebsd.org>  
wrote:

> On Fri, Apr 4, 2008 at 12:51 PM, Jeremy Messenger <mezz7 at cox.net> wrote:
>
>> On Fri, 04 Apr 2008 11:40:55 -0500, Christopher Arnold <chris at arnold.se>
>> wrote:
>>
>>
>> >
>> > On Fri, 4 Apr 2008, Jeremy Messenger wrote:
>> >
>> >  On Fri, 04 Apr 2008 11:24:12 -0500, Christopher Arnold  
>> <chris at arnold.se>
>> > > wrote:
>> > >
>> > >  On Fri, 4 Apr 2008, Denise H. G. wrote:
>> > > >
>> > > >  Christopher Arnold <chris at arnold.se> writes:
>> > > > >
>> > > > >  On Fri, 4 Apr 2008, Denise H. G. wrote:
>> > > > > >
>> > > > > >  Clint Olsen <clint.olsen at gmail.com> writes:
>> > > > > > >
>> > > > > > >  After a few days of portupgrading and cussing, I got things
>> > > > > > > > updated, but
>> > > > > > > > portupgrade takes eons because of these messages:
>> > > > > > > >  ===>   Registering installation for eel-2.22.1
>> > > > > > > > pkg_create: dependency loop detected for package
>> > > > > > > > libgnomeui-2.22.01:x11-toolkits/libgnomeui
>> > > > > > > > pkg_create: dependency loop detected for package
>> > > > > > > > gnome-desktop-2.22.0:x11/gnome-desktop
>> > > > > > > > pkg_create: dependency loop detected for package
>> > > > > > > > gnome-desktop-2.22.0:x11/gnome-desktop
>> > > > > > > > ===>  Cleaning for eel-2.22.1
>> > > > > > > >  Of course, nothing here tells me what is precisely  
>> looping.
>> > > > > > > >  Is it an
>> > > > > > > > immediate loop or indirect loop?
>> > > > > > > >
>> > > > > > > >  Manually run 'pkgdb -Fu'. It might help.
>> > > > > > >
>> > > > > > >  Following the information in /usr/pors/UPDATING takes care  
>> of
>> > > > > > the
>> > > > > > dependency loop...
>> > > > > > (And yes it includes pkgdb -Ff)
>> > > > > >  So it got me further, but i still have issues with compoiling
>> > > > > > gnome2,
>> > > > > > gnome2-power-tools and evince.
>> > > > > >  I belive evince is the showstopper here with:
>> > > > > > checking for gsapi_new_instance in -lgs... no
>> > > > > > configure: error: You need libgs in order to compile  
>> libspectre
>> > > > > >  Am i the only one? Or is everyone else also waiting for a  
>> final
>> > > > > > update
>> > > > > > taking care of this?
>> > > > > >
>> > > > >  I don't have problems compiling libspectre or evince. Have you
>> > > > > updated
>> > > > > your ports tree to the latest? My box is 7-STABLE/amd64.
>> > > > >
>> > > > >  Yes it is libspectre haveing a hard time to compile, evince and
>> > > > gnome depend on it.
>> > > >  Yes a completly fresh ports from today and im running on  
>> 6.3-STABLE
>> > > > from March the 16'th.
>> > > >
>> > >
>> > > Show us the output of 'pkg_info -IX ghostscript'.
>> > >
>> > >  ghostscript-gnu-7.07_17 GNU Postscript interpreter
>> >
>>
>> It explains... ahze only has change in ghostscript-gpl to enable with
>> library by default. Is there any reason why you don't use  
>> ghostscript-gpl
>> instead (/usr/ports/UPDATING at 20070405)? If you want to keep
>> ghostscript-gnu, try to reinstall it with WITH_SHLIB. I personal don't  
>> know
>> if libspectre will work with ghostscript-gnu.
>
>
> it won't build. you must use ghostscript-gpl

That USE_GHOSTSCRIPT=yes needs to be fix. Maybe we need to add a check of  
if -gnu exists then give user the better info of need to use -gpl instead  
in libspectre?

Cheers,
Mezz

> Michael
>
>
>>
>>
>> Cheers,
>> Mezz
>>
>>         /Chris


-- 
mezz7 at cox.net  -  mezz at FreeBSD.org
FreeBSD GNOME Team
http://www.FreeBSD.org/gnome/  -  gnome at FreeBSD.org