portupgrade & RO ports tree (was Re: [kris@freebsd.org: cvs commit: ports/Mk bsd.port.mk])

[Stijn Hoop]

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.

Sorry I was unclear -- what I meant was that I always use portupgrade on
a RO ports tree, and it worked from the beginning (IIRC).

> Kris, can we have a run of the ports-package system with a RO
> /usr/ports to see which ports fail because of this?

That would be great, but even better (IMHO) would be a run with PREFIX
set to a nonstandard value. In my experience most ports work with a RO
ports tree, but a lot less ports are PREFIX clean.

--Stijn

-- 
"What kind of a two-bit operation are they running out of this treehouse,
 Cooper? I have seen some slipshod backwater burgs, but this place takes the
 cake."
		-- Special Agent Albert Rosenfield, "Twin Peaks"
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 187 bytes
Desc: not available
Url : http://lists.freebsd.org/pipermail/freebsd-ports/attachments/20030422/4b44f927/attachment.bin