ports/54830: galeon2 port needs depends on nspr port

[Brian Reichert]

On Thu, Jul 24, 2003 at 06:47:04PM -0400, Joe Marcus Clarke wrote:
> On Thu, 2003-07-24 at 18:24, Brian Reichert wrote:
> > Ok, then why didn't 'portupgrade --new galeon2' cause my mozilla
> > port to be sufficiently upgraded, as to introduce nspr stuff?  Am
> > I completely misunderstanding how dependancies are utilized within
> > the ports system?
> 
> There could be a number of reasons, but most like because an older
> version of Mozilla was already installed.

That doesn't answer my question, unfortunately.

If 'galeon2' (however indirectly) depends on nspr, why isn't that
knowledge encoded in the ports tree?

Either galeon2 depends on nspr, or it depends on a sufficiently new
mozilla, where 'sufficiently new' is defined as 'in turn depends
on nspr'.

At least, that's what I've come to expect out of a dependancy-driven
system such that this...

> I like to do portupgrade -ra
> before adding nay new ports to the system because that way I'm sure
> everything is up-to-date.

I had in fact preceded this entire affair with 'portupgrade -ra'.

'galeon', did install, but proved to be buggy.  I noticed a 'galeon2'
port, so I installed _that_.  That's when the bitching about
libplds4.so.1 began.

Hence, my PR, and our subsequent conversation. :)

> 
> Joe
> 

-- 
Brian 'you Bastard' Reichert		<reichert at numachi.com>
37 Crystal Ave. #303			Daytime number: (603) 434-6842
Derry NH 03038-1713 USA			BSD admin/developer at large