From owner-freebsd-questions Sun Nov 14 1:15:54 1999 Delivered-To: freebsd-questions@freebsd.org Received: from ns.clientlogic.com (ns.clientlogic.com [207.51.66.75]) by hub.freebsd.org (Postfix) with ESMTP id 4EBEC14C93 for ; Sun, 14 Nov 1999 01:15:46 -0800 (PST) (envelope-from ChrisMic@clientlogic.com) Received: by site0s1 with Internet Mail Service (5.5.2650.21) id ; Sun, 14 Nov 1999 04:15:47 -0500 Message-ID: <6C37EE640B78D2118D2F00A0C90FCB4401105D7C@site2s1> From: Christopher Michaels To: 'Juha Saarinen' , "freebsd-questions@FreeBSD. ORG" Subject: RE: Ports and upgrading Date: Sun, 14 Nov 1999 04:19:11 -0500 MIME-Version: 1.0 X-Mailer: Internet Mail Service (5.5.2650.21) Content-Type: text/plain Sender: owner-freebsd-questions@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > -----Original Message----- > From: Juha Saarinen [SMTP:juha_saarinen@email.msn.com] > Sent: Sunday, November 14, 1999 3:56 AM > To: Christopher Michaels; freebsd-questions@FreeBSD. ORG > Subject: RE: Ports and upgrading > > Hiya Christopher, > > > Wait for the port to be updated. It's not just a matter of hacking > > make files, there are patches associated as well as other settings. > > Yep... noticed that. %-} > > > If you're impatient. Download the source code and compile it > > yourself, bypassing the ports collection all together. Although, > > an update > > to something like samba should make it into the collection fairly > quickly. > > > > As for replacing the old one. The commonly accepted way of doing > > this is the following. > > 1. make all, the new port, don't install. So you know it compiles. > > 2. Remove the old port with pkg_delete. > > 3. make install, the new port. > > 4. (Optional) make clean. > > I got Samba 2.0.6 and compiled it and installed it. Works fine, with a bit > of hacking of the paths. Samba 2.0.5a doesn't get along with FreeBSD very > well. 2.0.6 has a workaround for the MSG_WAIT bug (?)which lead to > weirdness > such as full speed when copying from the Samba server, but only a tenth > when > copying to it. > This was already addressed in one of the patches applied to the 2.0.5a version in the ports. But I am well aware of the bug as I had to patch it on my system before it made it's way into the ported version. I wasn't aware there was a 2.0.6 to be honest. :) Maybe they found a better fix for it. > > Now I know you haven't updated your ports with cvsup, either that or > > you haven't looked since updating. Because KDE 1.1.2 has been in > > there for > > a while. > > I have, I promise. Mind you, I've been using cvsup.au.freebsd.org. Mebbe > not > a recent tree? Or am I missing something again? I'm using the > ports-supfile > in the /usr/share/examples/cvsup directory. > That should be fine.. you could try synching with the main site just to see if there is a difference. > > Tell me about it. If it's a problem symlink /usr/ports/disfiles to > > a dir on a larger partition. Also, make sure you are doing a make clean > > after each port is installed. > > Yep... that's good advice. /home is almost empty so it'll have to take a > few > files I reckon. > Sounds good to me, that's what I did. > Cheers, > > -- Juha > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-questions" in the body of the message