Skip site navigation (1)Skip section navigation (2)
Date:      Thu, 7 Oct 2004 00:52:49 +0900
From:      Choy Kho Yee <khoyee@tf7.so-net.ne.jp>
To:        Renato Botelho <rbgarga@gmail.com>
Cc:        freebsd-questions@freebsd.org
Subject:   Re: Should I rebuild all ports?
Message-ID:  <C5F2F2F5-17AF-11D9-A351-000A95BE58A4@tf7.so-net.ne.jp>
In-Reply-To: <747dc8f304100608224a4e880e@mail.gmail.com>
References:  <051585EC-17A8-11D9-A351-000A95BE58A4@tf7.so-net.ne.jp> <747dc8f304100608224a4e880e@mail.gmail.com>

index | next in thread | previous in thread | raw e-mail

On 2004/10/07, at 0:22, Renato Botelho wrote:

> On Wed, 6 Oct 2004 23:57:19 +0900, Choy Kho Yee  
> <khoyee@tf7.so-net.ne.jp> wrote:
>> I have just upgraded FreeBSD 5.3BETA6 to BETA7.
>> According to /usr/src/UPDATING, some of the system
>> libraries have been upgraded, and we should rebuild
>> all ports if we want to use the new libraries. So,
>>
>>   1. should I rebuild all ports? (I think it should take one
>>       whole day...)
>>   2. If I am to rebuild all ports, what is the command I
>>       should use?
>
> Take a look at this message
> http://lists.freebsd.org/mailman/htdig/freebsd-current/2004-October/ 
> 039354.html
>
> There is a script made by Benjamin Lutz that checks all ports need to
> be rebuilded, so, you need to rebuild all these packages using
> portupgrade -f packagename, or use the /etc/libmap.conf.

Thanks for pointing me to the script!! I have saved the script to my  
computer,
run it and it said that there are 60 packages that I should upgrade. I  
will upgrade
them slowly when I have the spare time.

However, I still don't get how /etc/libmap.conf can be used to work  
around
this problem without rebuilding the ports.

Thanks.

---
Choy Kho Yee
url: http://dotkoyi.infoseek.ne.jp/
blog: http://dotkoyi.blogspot.com/

"There are only 10 types of people in the world, i.e. those who  
understand binary numbers and those who do not."


help

Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?C5F2F2F5-17AF-11D9-A351-000A95BE58A4>