Simon Krughoff, Kian-Tat Lim, what should we do with this RFC?

It sounded to me like the answer was "No." Is that a misunderstanding?

K-T laid out explicit plans for you to decide upon on his comment on 6th March.

Sorry. I was too glib. I meant the answer to the RFC as I formed it is "No" since I don't know of code that specifically depends on these packages in development. I filed this RFC specifically because I wanted to be able to depend on the stack dependencies and not do it in an ad-hoc manner as suggested in #3 above. There is a set of packages that resides in the interim between direct dependencies and tooling that everyone will eventually want at some point. This was my attempt to get at that with these packages that seem universally desired and recommended. If we are saying that they should be installed with the shared stack on lsst-dev and installed in the sciplat-lab image, they seem like actual dependencies to me. We have not, in the past, required an RFC to add packages to the sciplat-lab images in the past, so I'd prefer to just withdraw this RFC, and we can include packages where they are needed as we've done in the past.

Withdrawing this since I really was proposing adding these packages as third party dependencies to the stack as distributed by our standard distribution techniques.