Skip site navigation (1)Skip section navigation (2)
Date:      Thu, 02 Mar 2006 10:19:01 -0500
From:      Frank Laszlo <laszlof@vonostingroup.com>
To:        Ion-Mihai Tetcu <itetcu@people.tecnik93.com>
Cc:        Robert Huff <roberthuff@rcn.com>, freebsd-ports@freebsd.org
Subject:   Re: gtk lib rename.
Message-ID:  <44070CE5.6040308@vonostingroup.com>
In-Reply-To: <20060302042159.4329c6e7@it.buh.tecnik93.com>
References:  <20060301194643.5B40C2288F@snail.stack.nl>	<20060301222720.1675a5fe@it.buh.tecnik93.com>	<17414.6609.237542.150971@jerusalem.litteratus.org>	<20060302001848.4b05dbc6@it.buh.tecnik93.com>	<17414.11915.389608.88736@jerusalem.litteratus.org>	<20060302023909.19f2651a@it.buh.tecnik93.com>	<17414.20762.989110.599118@jerusalem.litteratus.org> <20060302042159.4329c6e7@it.buh.tecnik93.com>

next in thread | previous in thread | raw e-mail | index | archive | help
Could you point me to the thread that discussed this renaming? I'm
trying to figure out what exactly makes this new naming convention so
much better, as it seems to have caused more headache than helpfulness.

__________________________________________________
Frank Laszlo
System Administrator
The VonOstin Group
Email:  laszlof@tvog.net
WWW:    http://www.vonostingroup.com
Mobile: 248-863-7584



Ion-Mihai Tetcu wrote:
> On Wed, 1 Mar 2006 20:57:46 -0500
> Robert Huff <roberthuff@rcn.com> wrote:
>
>   
>> Ion-Mihai Tetcu writes:
>>
>>     
>>>  Please:
>>>  mv  /usr/local/lib/compat/pkg /usr/local/lib/compat/pkg.old
>>>  libchk > /tmp/libchk
>>>  grep Unresolvable /tmp/libchk | sed 's/.*: //' > /tmp/wrong_linked
>>>  sh -c 'for i in `cat /tmp/wrong_linked`; do \
>>>  		PKGNAME=`pkg_info -W $i`; \
>>>  		pkg_info -o ${PKGNAME} >>  /tmp/ports_to_upgrade;\
>>>  	done'
>>>  
>>>  and then please provide the /tmp/ports_to_upgrade as attachment
>>>  to your mail so I can process it easier :)
>>>       
>> 	Appended.
>>
>>     
>>>  You'll need to portupgrade -f each port fro that list (with the
>>>  exceptions of false positives).
>>>       
>> 	I'll start immediately.
>>     
>
> Better try portupgrade -Rfi and answer yes if the port is in the list.
> After you're finished, run libchk again.
>
>   
>> 	While I was running libchk, it spit out a whole bunch of
>> "Unreadable file or directory _______________".
>> 	Upon superficial examination, these _appear_ to be symlinks
>> whose target no longer exists.  Is this something I need to hunt
>> down, or can I just delete them?
>>     
>
> Since you didn't sent them, I can't tell.
>
>
>   



Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?44070CE5.6040308>