Date: Tue, 20 Nov 2012 13:47:19 +0100 From: Ollivier Robert <roberto@keltia.freenix.fr> To: Mohacsi Janos <mohacsi@niif.hu> Cc: freebsd-security@freebsd.org Subject: Re: Recent security announcement and csup/cvsup? Message-ID: <20121120124718.GB93826@roberto-aw.eurocontrol.fr> In-Reply-To: <alpine.DEB.2.00.1211201239110.26940@strudel.ki.iif.hu> References: <20121117150556.GE24320@in-addr.com> <alpine.BSF.2.00.1211171705170.32838@m.fuglos.org> <20121118180421.GF24320@in-addr.com> <20121120100148.GA93826@roberto-aw.eurocontrol.fr> <alpine.DEB.2.00.1211201239110.26940@strudel.ki.iif.hu>
next in thread | previous in thread | raw e-mail | index | archive | help
According to Mohacsi Janos on Tue, Nov 20, 2012 at 12:45:19PM +0100: > Dear Ollivier and all, > I have problem with the portsnap: I maintain a private "repository" > under the /usr/ports: There is a /usr/ports/tmp where I store new > ports to be tested, and submitted. The portsnap is removing > unrecognized local files. This is the main issue most preople have with portsnap, yes. > With cvsup I don't have such a problem. I use svn myself but I have access to the main FreeBSD repo. > I have no information about pkgng, whether I can maintain private > repository with pkgng or not? I don't know what portsnap does with things like .svn/.hg (from different VCS). If it does not remove them, use hg/git/svn to "merge" from the official portsnap tree into your own. If it does, just rsync periodically from portsnap into your /usr/ports. -- Ollivier ROBERT -=- FreeBSD: The Power to Serve! -=- roberto@keltia.net In memoriam to Ondine, our 2nd child: http://ondine.keltia.net/
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20121120124718.GB93826>