3 ms·

Also, besides apt-pinning, I sometimes just do a build-dep for certain softwares and build them manually, the good old way. ;) But obviously you try to avoid t

Also, besides apt-pinning, I sometimes just do a build-dep for certain softwares and build them manually, the good old way. ;) But obviously you try to avoid this in production environments if possible.

e12e 13y ago
Actually, I've become more and more a fan of "manually backporting" -- just throw apt-src registry for experimental in your sources, apt-get build-dep <package>;apt-get source <package>; cd <package>; dpkg-build. It only works for comparatively small packages, you'll need to keep an eye out yourself for security patches -- but it allows you to install stuff via dpkg -- and generally if the thing is too complex, you'll probably want to run a distribution package anyway (something simple in this context is nginx, varnish, nodejs (but I tend to run upstream nodejs -- too much of a moving target...) -- something complex might be pygame or network-manager -- basically stuff that has deep and wide dependencies. For stuff that I need to get from upstream, I try to use xstow -- it's a great way to keep either /usr/local or ~/opt/ manageable. Note: for nodejs -- it doesn't read the prefix variable for just make install, use DESTDIR (and do some manual cleanup): http://www.debian-administration.org/articles/682#comment_26 http://www.debian-administration.org/articles/682#comment_26
- e12e 13y ago
  I should add that yet another option is to use chroots, via schroot. It can get really hairy, but it can be the "easiest" way to get stuff like 32bit upstream wine running on a 64bit Debian box (without resorting to downright virtualization of some kind). https://wiki.debian.org/Schroot https://wiki.debian.org/Schroot http://www.debian-administration.org/article/schroot_-_chroot_for_any_users http://www.debian-administration.org/article/schroot_-_chroo... Note the warnings about going willy-nilly "xhost +". Much better to bind-mount home under the schroot(s) -- partially you'll probably want access to your home folder anyway (say Firefox or Chrome profile?) -- and it gives access to the X11 auth cookie keeping everything as (in)secure as it usually is.
  - voltagex_ 13y ago
    Docker seems like another good way to do this. Maybe I just fail at using schroot but I usually end up with a huge mess in /opt when I use it.
    - e12e 13y ago
      It does have a (too) steep learning curve. I second docker as an option.
- mindslight 13y ago
  I gave up on stow in favor of simply --prefix=/local/package-1.0.0 and adding that bin/ to $PATH in user-specific .zshenv. But this may only make sense as the packages I compile from source usually aren't dependencies for other packages. (Although if they were, I envision myself simply adding to LD_LIBRARY_PATH etc).
  - e12e 13y ago
    It's nice to have one (or a few) directory-hierarchies, (such as /usr/local) -- as you then can set LD_LIBRARY_PATH, MAN_PATH and PATH once, and have (most) everything just work. I find that the stuff that "only" needs to be added to path might as well just be symlinked to a "bin"-directory somewhere already in path. That said, I don't advocate doing things that are more complex than what is actually needed. For me xstow strikes a good balance.

e12e 13y ago

Actually, I've become more and more a fan of "manually backporting" -- just throw apt-src registry for experimental in your sources, apt-get build-dep <package>;apt-get source <package>; cd <package>; dpkg-build. It only works for comparatively small packages, you'll need to keep an eye out yourself for security patches -- but it allows you to install stuff via dpkg -- and generally if the thing is too complex, you'll probably want to run a distribution package anyway (something simple in this context is nginx, varnish, nodejs (but I tend to run upstream nodejs -- too much of a moving target...) -- something complex might be pygame or network-manager -- basically stuff that has deep and wide dependencies. For stuff that I need to get from upstream, I try to use xstow -- it's a great way to keep either /usr/local or ~/opt/ manageable. Note: for nodejs -- it doesn't read the prefix variable for just make install, use DESTDIR (and do some manual cleanup): http://www.debian-administration.org/articles/682#comment_26 http://www.debian-administration.org/articles/682#comment_26

e12e 13y ago
I should add that yet another option is to use chroots, via schroot. It can get really hairy, but it can be the "easiest" way to get stuff like 32bit upstream wine running on a 64bit Debian box (without resorting to downright virtualization of some kind). https://wiki.debian.org/Schroot https://wiki.debian.org/Schroot http://www.debian-administration.org/article/schroot_-_chroot_for_any_users http://www.debian-administration.org/article/schroot_-_chroo... Note the warnings about going willy-nilly "xhost +". Much better to bind-mount home under the schroot(s) -- partially you'll probably want access to your home folder anyway (say Firefox or Chrome profile?) -- and it gives access to the X11 auth cookie keeping everything as (in)secure as it usually is.
- voltagex_ 13y ago
  Docker seems like another good way to do this. Maybe I just fail at using schroot but I usually end up with a huge mess in /opt when I use it.
  - e12e 13y ago
    It does have a (too) steep learning curve. I second docker as an option.
mindslight 13y ago
I gave up on stow in favor of simply --prefix=/local/package-1.0.0 and adding that bin/ to $PATH in user-specific .zshenv. But this may only make sense as the packages I compile from source usually aren't dependencies for other packages. (Although if they were, I envision myself simply adding to LD_LIBRARY_PATH etc).
- e12e 13y ago
  It's nice to have one (or a few) directory-hierarchies, (such as /usr/local) -- as you then can set LD_LIBRARY_PATH, MAN_PATH and PATH once, and have (most) everything just work. I find that the stuff that "only" needs to be added to path might as well just be symlinked to a "bin"-directory somewhere already in path. That said, I don't advocate doing things that are more complex than what is actually needed. For me xstow strikes a good balance.