Date: Tue, 22 Apr 2003 16:47:56 +1000 From: Edwin Groothuis <edwin@mavetju.org> To: Kris Kennaway <kris@obsecurity.org> Cc: ports@freebsd.org Subject: Re: portupgrade & RO ports tree (was Re: [kris@freebsd.org: cvs commit: ports/Mk bsd.port.mk]) Message-ID: <20030422064756.GM762@k7.mavetju> In-Reply-To: <20030422064014.GA62078@rot13.obsecurity.org> References: <003b01c307f5$8c936e00$0480763e@semhome> <1050982709.421032.879.nullmailer@cicuta.babolo.ru> <20030422062152.GA18011@pcwin002.win.tue.nl> <20030422063428.GM808@k7.mavetju> <20030422064014.GA62078@rot13.obsecurity.org>
next in thread | previous in thread | raw e-mail | index | archive | help
On Mon, Apr 21, 2003 at 11:40:14PM -0700, Kris Kennaway wrote: > On Tue, Apr 22, 2003 at 04:34:28PM +1000, Edwin Groothuis wrote: > > On Tue, Apr 22, 2003 at 08:21:52AM +0200, Stijn Hoop wrote: > > > On Tue, Apr 22, 2003 at 07:38:29AM +0400, "."@babolo.ru wrote: > > > > > Maxim Sobolev wrote: > > > > > > Hm, execuse me my sarcasm, but do we really need the second portupgrade > > > > > > in C??? > > > > > > > > > > I see two main reasons: > > > > > 1) portupgrade is not in base system and never be there because of ruby. > > > > > 2) Because it is in ruby :) > > > > 3) Because it do not works on RO mounted /usr/ports > > > > > > It does. I have always run it in such a setup. > > > > No, it should. And ports which fail to build because of this should > > be fixed to use the WRKDIRPREFIX variable. > > > > Kris, can we have a run of the ports-package system with a RO > > /usr/ports to see which ports fail because of this? > > It always has, and none of them do :) In that case, I stand corrected. Edwin -- Edwin Groothuis | Personal website: http://www.mavetju.org edwin@mavetju.org | Weblog: http://www.mavetju.org/weblog/weblog.php
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20030422064756.GM762>