csup vs portsnap was: fresh install of kde4 fails -> japanese/kiten

Jim Pazarena fports at paz.bz
Wed Aug 29 17:27:32 UTC 2012

Alberto Villa wrote, On 2012-08-29 8:17 AM:
> On Wed, Aug 29, 2012 at 5:00 PM, Jim Pazarena <fports at paz.bz> wrote:
>> I use:  csup -g -L 2 ports-supfile
>> and ports-supfile
>> has all the recommended defaults, including "ports-all"
>> what am I missing?
> I don't know, maybe something went wrong in the past, but for sure
> that file (at least) is out of date. I suggest checking out a new
> ports tree with portsnap or Subversion.

A portsnap (which I have NEVER run in my life) fixed this issue.
I have always run cvsup and more recently csup.

I am concerned, now, because I would have assumed that csup
actually DOES update me, where it would seem that it has a failing,
at least WRT japanese/kiten

Which is the recommended way to stay PORT current? portsnap or csup?
I will switch to portsnap, but it is pretty slow compared to csup.


More information about the freebsd-ports mailing list