Re: Returning with question about SELECTIVELY updating ports tree

2011-01-19 Thread b. f.
> > 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 por

Re: Returning with question about SELECTIVELY updating ports tree

2011-01-19 Thread Alberto Villa
On Wed, Jan 19, 2011 at 1:33 AM, Mark Terribile wrote: > 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. the "install/uninstall" data, as you call it, is ma

Re: Returning with question about SELECTIVELY updating ports tree

2011-01-19 Thread RW
On Wed, 19 Jan 2011 08:35:21 + RW wrote: > On Wed, 19 Jan 2011 02:37:45 +0100 > Matthias Andree wrote: > > > Am 19.01.2011 01:33, schrieb Mark Terribile: > > > > > > Olli Hauer, > > > > > > I tried to reply to you directly as oha...@freebsd.org and > > > received the following error. My

Re: Returning with question about SELECTIVELY updating ports tree

2011-01-19 Thread RW
On Wed, 19 Jan 2011 02:37:45 +0100 Matthias Andree wrote: > Am 19.01.2011 01:33, schrieb Mark Terribile: > > > > Olli Hauer, > > > > I tried to reply to you directly as oha...@freebsd.org and received > > the following error. My message (edited a bit) follows the error. > > > > > > > > ---

Re: Returning with question about SELECTIVELY updating ports tree

2011-01-18 Thread Matthias Andree
Am 19.01.2011 01:33, schrieb Mark Terribile: > > Olli Hauer, > > I tried to reply to you directly as oha...@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 > {mx11

Re: Returning with question about SELECTIVELY updating ports tree

2011-01-18 Thread Xin LI
-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 On 01/18/11 15:43, Mark Terribile wrote: >> From: Xin LI >> Subject: Re: Returning with question about SELECTIVELY updating ports tree > >> On 01/18/11 15:00, Mark Terribile wrote: >> [...] >>> So: How do I

Re: Returning with question about SELECTIVELY updating ports tree

2011-01-18 Thread Mark Terribile
Olli Hauer, I tried to reply to you directly as oha...@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' ov

Re: Returning with question about SELECTIVELY updating ports tree

2011-01-18 Thread Olli Hauer
On 2011-01-19 00:00, Mark Terribile wrote: > > Hi, > [...] > > 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. > > Mark Terribile > Pro

Re: Returning with question about SELECTIVELY updating ports tree

2011-01-18 Thread Mark Terribile
> From: Xin LI > Subject: Re: Returning with question about SELECTIVELY updating ports tree > On 01/18/11 15:00, Mark Terribile wrote: > [...] > > So: How do I upgrade my ports system selectively, > without wiping out everything? > You can actually portsnap extract a

Re: Returning with question about SELECTIVELY updating ports tree

2011-01-18 Thread Xin LI
-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 On 01/18/11 15:00, Mark Terribile wrote: [...] > So: How do I upgrade my ports system selectively, without wiping out > everything? You can actually portsnap extract a part of the ports tree. e.g.: portsnap extract net/openldap24-server

Returning with question about SELECTIVELY updating ports tree

2011-01-18 Thread Mark Terribile
Hi, A while ago I came here with a question and got what seemed like good answers. After a number of distractions, I came back to the matter and discovered that the answers don't seem so good. So let me pose the case again, and if I have misunderstood you, or misunderstood the documentation