On Sunday, March 20, 2016 at 9:40:56 PM UTC, William wrote: > > On Fri, Mar 18, 2016 at 4:52 PM, Volker Braun <[email protected] > <javascript:>> wrote: > > On Friday, March 18, 2016 at 6:39:33 PM UTC+1, William wrote: > >> > >> 3. More generally, for SMC, it's useful, for the sake of Sage > >> development, to have a way to setup a sage dev environment as quickly > >> as possible for user experience reasons, and as efficiently as > >> possible to better make use of resources. > > > > > > There is precisely one way to do that right. Build Sage with a fixed > path > > (say, /sage-7.1) and then mount that as the lower filesystem of an > overlayfs > > inside the cgroup (with the same path obviously). And yes, thats > basically > > what docker is (plus some networking stuff). None of the user-space > hacks > > like copying the Sage directory tree come close. > > That doesn't work since SMC uses normal Linux users, not lxc or docker > containers, so they do not have a virtual chroot'd filesystem. >
I don't see why one would need anything non-standard (Linux) in order to use overlayfs. Seems to me I could use it on my desktop if I needed to have 5 active development branches of Sage. > > For most development (on the library, not on packaging, which is the > kind you probably do a lot of), a virtualenv (or python setup.py > develop) local setup of the sage library, which overrides a > system-wide install would be much better. It's just the completely > standard way in which Python libraries are developed after all. I > think you said you thought doing this would probably be low hanging > fruit, so I'm optimistic. > > -- William > > -- > William (http://wstein.org) > -- You received this message because you are subscribed to the Google Groups "sage-devel" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To post to this group, send email to [email protected]. Visit this group at https://groups.google.com/group/sage-devel. For more options, visit https://groups.google.com/d/optout.
