From owner-freebsd-ports@FreeBSD.ORG Wed Jan 19 00:33:54 2011 Return-Path: Delivered-To: freebsd-ports@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id B958D106566C for ; Wed, 19 Jan 2011 00:33:54 +0000 (UTC) (envelope-from materribile@yahoo.com) Received: from nm28.bullet.mail.sp2.yahoo.com (nm28.bullet.mail.sp2.yahoo.com [98.139.91.98]) by mx1.freebsd.org (Postfix) with SMTP id 9417B8FC0C for ; Wed, 19 Jan 2011 00:33:54 +0000 (UTC) Received: from [98.139.91.70] by nm28.bullet.mail.sp2.yahoo.com with NNFMP; 19 Jan 2011 00:33:54 -0000 Received: from [98.139.91.20] by tm10.bullet.mail.sp2.yahoo.com with NNFMP; 19 Jan 2011 00:33:54 -0000 Received: from [127.0.0.1] by omp1020.mail.sp2.yahoo.com with NNFMP; 19 Jan 2011 00:33:54 -0000 X-Yahoo-Newman-Property: ymail-3 X-Yahoo-Newman-Id: 329520.18151.bm@omp1020.mail.sp2.yahoo.com Received: (qmail 73668 invoked by uid 60001); 19 Jan 2011 00:33:53 -0000 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=yahoo.com; s=s1024; t=1295397233; bh=g0SQIzrDz1A1F3OzQIBc2/dzp41URcFK0ovb0R3FqEA=; h=Message-ID:X-YMail-OSG:Received:X-Mailer:Date:From:Subject:To:In-Reply-To:MIME-Version:Content-Type; b=ns+Jycoq94xceC9mTuNMKY64BBWzVAWpcyBJV8+Z9UAkXtpWrCzO7B0GmESTmlcYyzhvYX/WBBbqIrENHYMDJh5WqZF4svXaYn4yzQg8ikRteJaH3e1w85BvUZS1YKMTWkx4239wQprEk/flM3rSLwqc5V9+qasuf0OX8fYmiyQ= DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=s1024; d=yahoo.com; h=Message-ID:X-YMail-OSG:Received:X-Mailer:Date:From:Subject:To:In-Reply-To:MIME-Version:Content-Type; b=va99wUqf3GNotOKI84lRTOaqJ5S0j2tjVV2P5F0/+yRnzgNKRwAA19LCdouTXyK4Me9G6h1Y7nAH6G5bzmi3eBBGJyrxw1mCuH4S18e0zKflT5hpY3VpsuZkWY2IF9Wo9a8nQoLhBGzP7d17eyHThh5erNg5pH4zqXGhaMhP9Hw=; Message-ID: <928239.73646.qm@web110308.mail.gq1.yahoo.com> X-YMail-OSG: eEhm9wwVM1mG2nhZwPNvLKOd6J0TvW50wMCnN019IzX5isX wjW.4dKcI4RfsGCJUFe7y_N41BGvGNwH8auEoOq28JE7PpPotZsD5ZbQGe4X tija0kxN.VGh.tUML.k6ZKA2GtaIaB_ZyDiDB6Mj2jLcFOjj.3pAop1PHzQ3 FqYw148JqXX1qasckEJGdIIcz2h2znUDoUPIZ9BWmqrogwJyTBwFyXbLDd3O F.z9qmCZM8zFgmRYz8E3._RErnbeajRxSuiuAjE_jfL5ngjLd9cZy5jpPc7S dGLpY1KzHGzyoDRqWhOUDL3p45OCfrbNMjRTNoBQzG_BpSEK4Y_HuT8rnvm1 ISgc1nOgCypl__ymro.7b0C_wpCf7bm8B3zOzUL4gL1BlI81I8EkL2tKiuzt Hy9HWHopF Received: from [24.228.57.153] by web110308.mail.gq1.yahoo.com via HTTP; Tue, 18 Jan 2011 16:33:53 PST X-Mailer: YahooMailClassic/11.4.20 YahooMailWebService/0.8.107.285259 Date: Tue, 18 Jan 2011 16:33:53 -0800 (PST) From: Mark Terribile To: freebsd-ports@freebsd.org In-Reply-To: <4D3626AE.1050709@FreeBSD.org> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Subject: Re: Returning with question about SELECTIVELY updating ports tree X-BeenThere: freebsd-ports@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Porting software to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 19 Jan 2011 00:33:54 -0000 Olli Hauer, I tried to reply to you directly as ohauer@FreeBSD.org and received the following error. My message (edited a bit) follows the error. --------------- --- : host mx1.gmx.net[213.165.64.102] said: 550-5.7.1 {mx113} The --- recipient does not accept mails from 'yahoo.com' over foreign mailservers --- 550 5.7.1 ( http://portal.gmx.net/serverrules ) (in reply to RCPT TO --- command) --------------- Olli, > > If there is a way to do this with portsnap, please > tell me how. I've tried the -I option but it seems to > want me to do the extract which (according to the man page) > will wipe out the whole tree. > Protect your ports tree > $> cd /usr/ > $> mv ports ports_save && mkdir ports && > portsnap extract > > > This way you have your old and a fresh ports tree > available. > Portsnap checks the file ports/.portsnap.INDEX to see > which > ports have updates without this file portsnap extracts the > whole tree. > > Now you can check with diff what has changed in your > needed > ports. In most of the cases you can merge the ports in the > saved tree to newer versions. When you do that, don't you mess up the "install/uninstall" data? The new port may not know how to uninstall the old one correctly, or even understand that the old one is installed. Or am I missing something? I went through something like this a while ago, with a massive set of uncontrolled rebuilds. My shared libraries and executables were bolixed and after two days of trying to get X (and X apps and other things) running again I gave up and reloaded from backup. I don't want to go that route again. Here's my point of confusion: My understanding is that portupgrade understands how to rebuild ports and manage their dependencies. It's not perfect, but it's far more right than wrong. And the key to portupgrade is whatever ports-available/dependent list it uses. So shouldn't The Right Thing To Do be to fetch and install just the upgrade to that list? But smashing everything blindly (which portsnap extract would seem to do) not only does an end run around portupgrade, it completely thwarts it. Doesn't it? Mark