On Tue, Feb 16, 2021 at 05:52:21PM -0500, Stefan Monnier wrote: [...]
> > I have the hunch that just making the packages co-installable is > > the more pleasant avenue... > > It's more pragmatic, but it won't solve the longer-term recurring issues. I think I was too cryptic, sorry: I meant co-installable as, e.g. PostgreSQL does with its different versions: you have to crack the resources nut anyway, and then, what's the "alternatives" thing for, anyway? Alternatives make only sense in the presence of user interaction: I invoke "vi" and get presented with whatever-incarnation-of-vi is currently The One. I invoke "man vi", likewise. Still, I can invoke (explicitly) "vim", "man vim". What I meant by co-installable: both MTAs are up and running, each one possibly with an own listening port [1], each one with a different /var/spool/<mta-of-the-day>/mail. Or something. No alternatives. Cheers [1] Other avenues seem worth considering, i.e. some kind of protocol proxy which dispatches to the different MTAs based on first handshake steps, what not. - t
signature.asc
Description: Digital signature
