<p><br>
On Dec 16, 2013 9:17 PM, "Samuel Greenfeld" <<a href="mailto:samuel@greenfeld.org">samuel@greenfeld.org</a>> wrote:<br>
><br>
> From the end user's perspective, what virtualenv does is rewrite the Python path & environment so a series of custom-created directories are always tried first. It then optionally looks at the system python path for other modules.<br>
><br>
> The one time I had to use virtualenv it did not solve problems with libraries that needed to compile machine-specific code. It might be possible to use pip with prepackaged binaries, but the project I was using it with did not offer the option.<br>
><br>
><br>
> Packaging admittedly is a bit over my head. But the more XSCE deviates from being directly packagable in a Linux Distribution, the more work it is going to take to maintain this path.<br>
><br>
> I think it would be worthwhile to look at the Linux Terminal Server Project (<a href="http://www.ltsp.org">www.ltsp.org</a>) and see how they packaged their system so that it was accepted into several distributions. The LTSP project interfaces with a lot of components (DHCP, X Server, etc.) and has been around since 1999, so they have experience doing the kind of tweaks XSCE also needs to make.<br>
></p>
<p>LTSP uses chroot to contain the OS being served. We run a lab of 32 machines on it. Quite stable and runs well. </p>
<p>There's also LXC, a "chroot on steroids", as stgraber puts it. <a href="https://www.stgraber.org/2013/12/20/lxc-1-0-blog-post-series/">https://www.stgraber.org/2013/12/20/lxc-1-0-blog-post-series/</a></p>
<p>Sameer <br>
><br>
><br>
><br>
><br>
> On Mon, Dec 16, 2013 at 1:53 PM, Miguel González <<a href="mailto:migonzalvar@activitycentral.com">migonzalvar@activitycentral.com</a>> wrote:<br>
>><br>
>> On Mon, Dec 16, 2013 at 6:16 PM, Braddock <<a href="mailto:braddock@braddock.com">braddock@braddock.com</a>> wrote:<br>
>> > -----BEGIN PGP SIGNED MESSAGE-----<br>
>> > Hash: SHA1<br>
>> ><br>
>> > If this can be made to work it would certainly make things easier for<br>
>> > us at Internet-in-a-Box.<br>
>> ><br>
>><br>
>> Quick test in XO-4 using the following script, it seems it works perfectly:<br>
>><br>
>> mkdir iiab<br>
>> cd iiab<br>
>> virtualenv venv<br>
>> source venv/bin/activate<br>
>> pip install --use-wheel --no-index<br>
>> --find-links=<a href="http://xsce.activitycentral.com/wheelhouse/">http://xsce.activitycentral.com/wheelhouse/</a><br>
>> 'backports.lzma>=0.0.2' 'SQLAlchemy>=0.8.2' 'markupsafe'<br>
>> pip install Internet-in-a-Box<br>
>> iiab-server<br>
>> ...<br>
>> werkzeug -- 192.168.0.3 - - [16/Dec/2013 18:40:19] "GET /iiab/ HTTP/1.1" 200 -<br>
>><br>
>> I'm attaching the full log.<br>
>><br>
>> I plan to do more testing. I think we could use this method for latter<br>
>> XSCE versions.<br>
>><br>
>> > Currently we have to build and distribute Fedora rpms just for XSCE,<br>
>> > including for a couple third party packages which have binary<br>
>> > dependencies and have proven a pain.<br>
>> ><br>
>> > We already maintain pipy pip packages and use them for all of our own<br>
>> > IIAB appliance deployments.<br>
>> ><br>
>> > However, a virtualenv is not really meant as a distribution format and<br>
>> > has some downsides. You will have to install the pip on every<br>
>> > architecture you support, and I do not believe they are relocatable so<br>
>> > they have to be in the same absolute path, and they may have system<br>
>> > library dependencies which won't automatically be resolved like with RPMs.<br>
>> ><br>
>> > Given the fragility and dependency hell of the RPM method though, I<br>
>> > think it is worthwhile to switch to virtualenvs.<br>
>> ><br>
>> > - -braddock<br>
>> ><br>
>> ><br>
>> >> From: Miguel Gonz?lez <<a href="mailto:migonzalvar@activitycentral.com">migonzalvar@activitycentral.com</a>><br>
>> >><br>
>> >> I want to share with you my proposed approach to install Python<br>
>> >> web application in XSCE.<br>
>> >><br>
>> >><br>
>> >> The idea is to install them into a Python virtual environment<br>
>> >> isolated from the system wide packages installed.<br>
>> ><br>
>> > -----BEGIN PGP SIGNATURE-----<br>
>> > Version: GnuPG v1.4.11 (GNU/Linux)<br>
>> > Comment: Using GnuPG with Thunderbird - <a href="http://www.enigmail.net/">http://www.enigmail.net/</a><br>
>> ><br>
>> > iQEcBAEBAgAGBQJSrzWJAAoJEHWLR/DQzlZu2i8H/iuxZPLPnu60JzE4UiqpDo3v<br>
>> > sPxqJgOjSA/lNj/icpl1EY0AaPUgcUWIOnmF2loYSMwR6AfzUbLH35OuPfXVZ8cY<br>
>> > +3eSbT+BnqiQiV+vpsVJQ7NFYipICetldzN4jlhGLgFpVCRgwvDaQCLrgw0MY67y<br>
>> > 6xmkI+e4g01i4q4DLA8+jEtlDGeVYWdTmcugka4a/w9UDKIBIfmZ2LCsZq/XoZxB<br>
>> > p895BjYHWk/RSYGC3GC8o1pmXksUIMzf211Lkw3aunXD5G9+tW1ozSktcMEDxAlr<br>
>> > DAXDduyOemEzLa5o1KdMsMbq9ENpBegY3ekejL9ftaN1uyebXVXDD/t32roAVD8=<br>
>> > =9YGH<br>
>> > -----END PGP SIGNATURE-----<br>
>> > _______________________________________________<br>
>> > Server-devel mailing list<br>
>> > <a href="mailto:Server-devel@lists.laptop.org">Server-devel@lists.laptop.org</a><br>
>> > <a href="http://lists.laptop.org/listinfo/server-devel">http://lists.laptop.org/listinfo/server-devel</a><br>
>><br>
>> --<br>
>> Miguel González<br>
>> Activity Central: <a href="http://www.activitycentral.com">http://www.activitycentral.com</a><br>
>><br>
>> _______________________________________________<br>
>> Server-devel mailing list<br>
>> <a href="mailto:Server-devel@lists.laptop.org">Server-devel@lists.laptop.org</a><br>
>> <a href="http://lists.laptop.org/listinfo/server-devel">http://lists.laptop.org/listinfo/server-devel</a><br>
>><br>
><br>
><br>
> _______________________________________________<br>
> Server-devel mailing list<br>
> <a href="mailto:Server-devel@lists.laptop.org">Server-devel@lists.laptop.org</a><br>
> <a href="http://lists.laptop.org/listinfo/server-devel">http://lists.laptop.org/listinfo/server-devel</a><br>
><br>
</p>