Date: Mon, 21 Apr 2003 23:40:14 -0700 From: Kris Kennaway <kris@obsecurity.org> To: Edwin Groothuis <edwin@mavetju.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: <20030422064014.GA62078@rot13.obsecurity.org> In-Reply-To: <20030422063428.GM808@k7.mavetju> References: <003b01c307f5$8c936e00$0480763e@semhome> <1050982709.421032.879.nullmailer@cicuta.babolo.ru> <20030422062152.GA18011@pcwin002.win.tue.nl> <20030422063428.GM808@k7.mavetju>
next in thread | previous in thread | raw e-mail | index | archive | help
--VS++wcV0S1rZb1Fb Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable 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 portu= pgrade > > > > > in C??? > > > >=20 > > > > 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 > >=20 > > It does. I have always run it in such a setup. >=20 > No, it should. And ports which fail to build because of this should > be fixed to use the WRKDIRPREFIX variable. >=20 > 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 :) Kris --VS++wcV0S1rZb1Fb Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.2.1 (FreeBSD) iD8DBQE+pOPOWry0BWjoQKURAudgAKDWUzirR0GihAykNXu6Fto8dVU28wCffaWw X56PV6pNzpDqkZ9yt2Wd0D4= =dtLO -----END PGP SIGNATURE----- --VS++wcV0S1rZb1Fb--
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20030422064014.GA62078>