> I think, actually, it might be better served as a one-or-the-other > installation, unless there's ever any good reason why you'd have two copies > installed at once. The incorporations defining the latest Indiana / Nevada > builds could constrain squid to being 2.6, but people could choose 3.x > instead if they so chose.
The scenario I was thinking was where you might run different versions of Squid on different ports of the same system (one in production, one in dev?) Of course, I would prefer putting such services in different zones :-) but that does mean extra IP addresses. dsc
