1. Working as a hobby developer on Debian/Jessie64
    1. mostly C++ but also assembly, python, java, c, c#
    2. like compiling programs on my own like
    3. looking into other's source

it results into many packages(libraries/tools) installed and so making the system slow (look for a library in a folder with a few hundred libs is faster than a thousands of - same for bin)

how do you keep your machine clean? remembering packages and uninstalling (complicated, time consuming)? apt-get autoremove? also removes additional packages not "needed" but useful

using virtualbox for a dev-machine?

is it possible, to tell gcc to look for headers on a different machine and the same for ld for the libraries to link?


with "slower" I mean that programs (browsers, IDE) start a bit slower (not measured)

I already use vagrant for working with LAMP stacks or other things I definitely don't want on my machine

Didn't think about chrooting for a dev-env, definitely have to try this.

closed as unclear what you're asking by Jeff Schaller, jimmij, vonbrand, polemon, mdpc Jan 8 '16 at 23:41

Please clarify your specific problem or add additional details to highlight exactly what you need. As it's currently written, it’s hard to tell exactly what you're asking. See the How to Ask page for help clarifying this question. If this question can be reworded to fit the rules in the help center, please edit the question.

  • 1
    How much slower? Did you time anything, or does it just "feel" slower? – drewbenn Jan 8 '16 at 20:06
  • 1
    Use vagrant with VirtualBox. Single command to create a clean environment. Single command to destroy it so you can start again fresh. – Wildcard Jan 8 '16 at 21:43
  • 1
    Unless you install many thousands of libraries in /usr/lib, you'd not be able to notice any slowdown. – vonbrand Jan 8 '16 at 22:03

One possible idea is to create a chroot environment, in which you chroot to, install whatever you need to, do your dev work, and then exit when your done. This should leave everything outside of the chroot environment unaffected.


I don't bother. Linux is very efficient at things like caching library lookups, so I doubt you would be able to notice any difference. Everything you've suggested adds lots of overhead (VMs are slow to start up; VMs and chroots and containers are logically separate machines and need to be kept up-to-date with security updates; putting headers or libraries on a network machine adds lots of network latency whenever you try to access them).

The only things you should notice are that tab-complete will return more results and your GUI application menus will get more entries. If those sorts of things bother you, then sure, remove applications you don't think you'll need anymore.

Not the answer you're looking for? Browse other questions tagged or ask your own question.