Coming from #185

#185 (comment)
Let me rephrase, what @mithro mentions is an issue with additional env variables that maybe we can improve to not have to define.

What you propose is a change in the approach and a different discussion. By design this repo ("symbiflow-examples") was/is supposed to show users how to install Symbiflow toolchain(s) using conda (a packaging system that is distro-independent) on multiple different distros and then how to use the toolchain with a range of example designs.

Btw maybe I am alone here but I personally (as a user) would not care if the containers are built by using conda inside or not. The whole point of the containers is a little bit that you do not care whats inside as long as it works. Its a glorified "wget a big rootfs + chroot + forget" in many cases.

And do not get me wrong, I like containers. I am just explaining rationale behind what symbiflow-examples tries/tried to be. I think this discussion could be moved into a separate issue tbh.

@pgielda, do you suggest a symbiflow-examples-with-containers repo to be created in order to showcase how to build the same HDL sources from this repo using SymbiFlow on containers instead of "locally"?

I thought that the scope of this repo included building the same example using SymbiFlow by any "environment installation" procedure. Similarly to fomu-workshop, which shows 3-6 different strategies. In other words, I thought that this repo was directly related to SymbiFlow/make-env (mithro/make-env#15, mithro/make-env#24 and #49). Anyway, I'm good with submoduling this repo and adding make-env + container stuff somewhere else.