ghen@NetBSD.org said:
> I'd prefer the simplest way, i.e. just registering the www/firefox2
> package as firefox-2.0 and leaving the rest untouched: 

fine, just the PLIST change is missing

> As for the bl3 files, you're right, but I think it would indeed be harmless in
> this case.  Btw how do we handle this with other library packages of which we
> provide multiple versions?

It is a rare case that a program can be built against different
major versions of the same library. In at least one case (Python)
there is a central buildlink File (as application.mk) which
pulls in a specific one.

In the firefox case, the firefox-1 will probably be deleted anyway
in the near future, so it is not worth to bother with the framework
too much.

best regards
Matthias