如何备份/还原python virtualenv? [英] How to backup/restor python virtualenv?

问题描述

python virtualenv充满了符号链接:

A python virtualenv is full of symlinks:

$ virtualenv venv
Running virtualenv with interpreter /usr/bin/python2
New python executable in venv/bin/python2
Also creating executable in venv/bin/python
Installing setuptools, pip...done.
$ tree venv/lib/
venv/lib/
├── python2.7
│   ├── _abcoll.py -> /usr/lib/python2.7/_abcoll.py
│   ├── _abcoll.pyc
│   ├── abc.py -> /usr/lib/python2.7/abc.py
│   ├── abc.pyc
│   ├── codecs.py -> /usr/lib/python2.7/codecs.py
│   ├── codecs.pyc
│   ├── copy_reg.py -> /usr/lib/python2.7/copy_reg.py
│   ├── copy_reg.pyc
│   ├── distutils
│   │   ├── distutils.cfg
│   │   ├── __init__.py
│   │   └── __init__.pyc
│   ├── encodings -> /usr/lib/python2.7/encodings
│   ├── fnmatch.py -> /usr/lib/python2.7/fnmatch.py
│   ├── fnmatch.pyc
│   ├── genericpath.py -> /usr/lib/python2.7/genericpath.py
│   ├── genericpath.pyc

推荐的备份/还原方式是什么?

What is the recommended way to backup/restor them ?

当我还原备份时，我第一次尝试使用rdiff-backup取消了所有符号链接的引用.

My first attempt using rdiff-backup has derefence all symbolic links when I restor backup back.

推荐答案

rdiff-backup通常按原样复制符号链接，而不引用它们.您是否可能添加了--include-symlinks选项?

rdiff-backup normally copies symlinks as they are and does not reference them. Did you maybe add the --include-symlinks option ?

"cp -p"或"rsync -a"也将保留符号链接.

"cp -p" or "rsync -a" would also preserve symlinks.

这篇关于如何备份/还原python virtualenv?的文章就介绍到这了，希望我们推荐的答案对大家有所帮助，也希望大家多多支持IT屋！