× The internal search function is temporarily non-functional. The current search engine is no longer viable and we are researching alternatives.
As a stop gap measure, we are using Google's custom search engine service.
If you know of an easy to use, open source, search engine ... please contact support@midrange.com.



Hi, Niels,

I thought I mentioned chroot in one of my replies ... ?

But it was my impression that "chroot" creates a temporary environment, such that once you exit "chroot", it is "gone" and you would then need to re-install, or copy everything you need to use, back into that "chroot" set of directories and environment, to use it?

Thanks,

Mark S. Waterbury






On Friday, December 18, 2020, 4:48:28 PM EST, Niels Liisberg <nli@xxxxxxxxxxxxxxxxx> wrote:





chroot anyone?

I am just curious if it might be better to jail it. Then you will look at a
vanilla system in your own root

Any comments on that?


fre. 18. dec. 2020 kl. 21.49 skrev John Yeung <gallium.arsenide@xxxxxxxxx>:

On Fri, Dec 18, 2020 at 3:22 PM Mark Waterbury
<mark.s.waterbury@xxxxxxxxxxxxx> wrote:

So you can quickly end up installing one OSS package, then at some other
time, you try to install a different OSS package, and now either it refuses
to install, saying there is a conflict, or even worse, the first one quits
working because you inadvertently updated something that it "depends on."

My recommendation for how to avoid this is to use a separate
sub-directory for each "set" of related OSS tools, and install all the
needed stuff into there ... then you can just zip it all up, (or in Unix
terms, create one big "tarball"), and if you need to install it on another
system, just unzip or untar it all again.  In other words, each product or
tool has its own "top-level" directory that contains ALL of the
"dependencies" needed for that tool.  So, it is "self-contained."  (Sure,
it uses more disk space, but it solves a lot of problems and saves a lot of
frustration, long term.)

That is the venv concept precisely. In the case of Python, pip and
venv complement each other. venv makes it easy to create and select
among these isolated subdirectories; pip makes it easy to install
packages into the currently active venv.

And naturally, there are efforts to make things even easier still. The
two leading projects in the "pip-and-venv-superset" space are probably
Pipenv and Poetry. (I believe Kevin is trying to move in the direction
of using Poetry for IBM's Python projects.)

John Y.
--
This is the IBMi Open Source Roundtable (OpenSource) mailing list
To post a message email: OpenSource@xxxxxxxxxxxxxxxxxx
To subscribe, unsubscribe, or change list options,
visit: https://lists.midrange.com/mailman/listinfo/opensource
or email: OpenSource-request@xxxxxxxxxxxxxxxxxx
Before posting, please take a moment to review the archives
at https://archive.midrange.com/opensource.

Help support midrange.com by shopping at amazon.com with our affiliate
link: https://amazon.midrange.com



As an Amazon Associate we earn from qualifying purchases.

This thread ...

Follow-Ups:
Replies:

Follow On AppleNews
Return to Archive home page | Return to MIDRANGE.COM home page

This mailing list archive is Copyright 1997-2024 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact [javascript protected email address].

Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.