document/TranslateProject
2
0
Fork 0
mirror of https://github.com/LCTT/TranslateProject.git synced 2024-12-26 21:30:55 +08:00
Code Issues Packages Projects Releases Wiki Activity

Merge pull request #8144 from MjSeven/master

Browse Source 
20171007 How to use GNU Stow to manage programs installed from source and dotfiles.md 翻译完毕
This commit is contained in:
Xingyu.Wang 2018-03-16 09:57:11 +08:00 committed by GitHub
commit c8b9640b57
No known key found for this signature in database
GPG Key ID: 4AEE18F83AFDEB23
2 changed files with 131 additions and 144 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

144
sources/tech/20171007 How to use GNU Stow to manage programs installed from source and dotfiles.md
View File

@ -1,144 +0,0 @@
Translating by MjSeven
How to use GNU Stow to manage programs installed from source and dotfiles
======
### Objective
Easily manage programs installed from source and dotfiles using GNU stow
### Requirements
* Root permissions
### Difficulty
EASY
### Conventions
* **#** \- requires given command to be executed with root privileges either directly as a root user or by use of `sudo` command
* **$** \- given command to be executed as a regular non-privileged user
### Introduction
Sometimes we have to install programs from source: maybe they are not available through standard channels, or maybe we want a specific version of a software. GNU stow is a very nice `symlinks factory` program which helps us a lot by keeping files organized in a very clean and easy to maintain way.
### Obtaining stow
Your distribution repositories is very likely to contain `stow`, for example in Fedora, all you have to do to install it is:
```
# dnf install stow
```
or on Ubuntu/Debian you can install stow by executing:
```
# apt install stow
```
In some distributions, stow it's not available in standard repositories, but it can be easily obtained by adding some extra software sources (for example epel in the case of Rhel and CentOS7) or, as a last resort, by compiling it from source: it requires very little dependencies.
### Compiling stow from source
The latest available stow version is the `2.2.2`: the tarball is available for download here: `https://ftp.gnu.org/gnu/stow/`.
Once you have downloaded the sources, you must extract the tarball. Navigate to the directory where you downloaded the package and simply run:
```
$ tar -xvpzf stow-2.2.2.tar.gz
```
After the sources have been extracted, navigate inside the stow-2.2.2 directory, and to compile the program simply run:
```
$ ./configure
$ make
```
Finally, to install the package:
```
# make install
```
By default the package will be installed in the `/usr/local/` directory, but we can change this, specifying the directory via the `--prefix` option of the configure script, or by adding `prefix="/your/dir"` when running the `make install` command.
At this point, if all worked as expected we should have `stow` installed on our system
### How does stow work?
The main concept behind stow it's very well explained in the program manual:
```
The approach used by Stow is to install each package into its own tree,
then use symbolic links to make it appear as though the files are
installed in the common tree.
```
To better understand the working of the package, let's analyze its key concepts:
#### The stow directory
The stow directory is the root directory which contains all the `stow packages`, each with their own private subtree. The typical stow directory is `/usr/local/stow`: inside it, each subdirectory represents a `package`
#### Stow packages
As said above, the stow directory contains "packages", each in its own separate subdirectory, usually named after the program itself. A package is nothing more than a list of files and directories related to a specific software, managed as an entity.
#### The stow target directory
The stow target directory is very a simple concept to explain. It is the directory in which the package files must appear to be installed. By default the stow target directory is considered to be the one above the directory in which stow is invoked from. This behaviour can be easily changed by using the `-t` option (short for --target), which allows us to specify an alternative directory.
### A practical example
I believe a well done example is worth 1000 words, so let's show how stow works. Suppose we want to compile and install `libx264`. Lets clone the git repository containing its sources:
```
$ git clone git://git.videolan.org/x264.git
```
Few seconds after running the command, the "x264" directory will be created, and it will contain the sources, ready to be compiled. We now navigate inside it and run the `configure` script, specifying the /usr/local/stow/libx264 directory as `--prefix`:
```
$ cd x264 && ./configure --prefix=/usr/local/stow/libx264
```
Then we build the program and install it:
```
$ make
# make install
```
The directory x264 should have been created inside of the stow directory: it contains all the stuff that would have been normally installed in the system directly. Now, all we have to do, is to invoke stow. We must run the command either from inside the stow directory, by using the `-d` option to specify manually the path to the stow directory (default is the current directory), or by specifying the target with `-t` as said before. We should also provide the name of the package to be stowed as an argument. In this case we run the program from the stow directory, so all we need to type is:
```
# stow libx264
```
All the files and directories contained in the libx264 package have now been symlinked in the parent directory (/usr/local) of the one from which stow has been invoked, so that, for example, libx264 binaries contained in `/usr/local/stow/x264/bin` are now symlinked in `/usr/local/bin`, files contained in `/usr/local/stow/x264/etc` are now symlinked in `/usr/local/etc` and so on. This way it will appear to the system that the files were installed normally, and we can easily keep track of each program we compile and install. To revert the action, we just use the `-D` option:
```
# stow -d libx264
```
It is done! The symlinks don't exist anymore: we just "uninstalled" a stow package, keeping our system in a clean and consistent state. At this point it should be clear why stow it's also used to manage dotfiles. A common practice is to have all user-specific configuration files inside a git repository, to manage them easily and have them available everywhere, and then using stow to place them where appropriate, in the user home directory.
Stow will also prevent you from overriding files by mistake: it will refuse to create symbolic links if the destination file already exists and doesn't point to a package into the stow directory. This situation is called a conflict in stow terminology.
That's it! For a complete list of options, please consult the stow manpage and don't forget to tell us your opinions about it in the comments.
--------------------------------------------------------------------------------
via: https://linuxconfig.org/how-to-use-gnu-stow-to-manage-programs-installed-from-source-and-dotfiles
作者：[Egidio Docile][a]
译者：[译者ID](https://github.com/译者ID)
校对：[校对者ID](https://github.com/校对者ID)
本文由 [LCTT](https://github.com/LCTT/TranslateProject) 原创编译，[Linux中国](https://linux.cn/) 荣誉推出
[a]:https://linuxconfig.org

131
translated/tech/20171007 How to use GNU Stow to manage programs installed from source and dotfiles.md Normal file
View File

@ -0,0 +1,131 @@
如何使用 GNU Stow 来管理从源代码和 dotfiles 安装的程序
=====
dotfiles(**.**开头的文件在 *nix 下默认为隐藏文件)
### 目的
使用 GNU Stow 轻松管理从源代码和 dotfiles 安装的程序
### 要求
* root 权限
### 难度
简单
### 约定
* **#** \- 要求直接以 root 用户身份或使用 `sudo` 命令以 root 权限执行给定的命令
* **$** \- 给定的命令将作为普通的非特权用户来执行
### 介绍
有时候我们必须从源代码安装程序，因为它们也许不能通过标准渠道获得，或者我们可能需要特定版本的软件。 GNU Stow 是一个非常不错的 `symlinks factory` 程序，它可以帮助我们保持文件的整洁，易于维护。
### 获得 stow
你的 Linux 发行版本很可能包含 `stow`，例如在 Fedora，你安装它只需要：
```
# dnf install stow
```
在 Ubuntu/Debian 中，安装 stow 需要执行：
```
# apt install stow
```
在某些 Linux 发行版中，stow 在标准库中是不可用的，但是可以通过一些额外的软件源（例如 Rhel 和 CentOS7 中的epel ）轻松获得，或者，作为最后的手段，你可以从源代码编译它。只需要很少的依赖关系。
### 从源代码编译
最新的可用 stow 版本是 `2.2.2`。源码包可以在这里下载：`https://ftp.gnu.org/gnu/stow/`。
一旦你下载了源码包，你就必须解压它。切换到你下载软件包的目录，然后运行：
```
$ tar -xvpzf stow-2.2.2.tar.gz
```
解压源文件后，切换到 stow-2.2.2 目录中，然后编译该程序，只需运行:
```
$ ./configure
$ make
```
最后，安装软件包：
```
# make install
```
默认情况下，软件包将安装在 `/usr/local/` 目录中，但是我们可以改变它，通过配置脚本的 `--prefix` 选项指定目录，或者在运行 `make install` 时添加 `prefix="/your/dir"`。
此时，如果所有工作都按预期工作，我们应该已经在系统上安装了 `stow`。
### stow 是如何工作的？
stow 背后主要的概念在程序手册中有很好的解释：
```
Stow 使用的方法是将每个软件包安装到自己的树中，然后使用符号链接使它看起来像文件一样安装在普通树中
```
为了更好地理解这个软件的运作，我们来分析一下它的关键概念：
#### stow 文件目录
stow 目录是包含所有 `stow 包` 的根目录，每个包都有自己的子目录。典型的 stow 目录是 `/usr/local/stow`：在其中，每个子目录代表一个 `package`。
#### stow 包
如上所述，stow 目录包含多个 "包"，每个包都位于自己单独的子目录中，通常以程序本身命名。包不过是与特定软件相关的文件和目录列表，作为实体进行管理。
#### stow 目标目录
stow 目标目录解释起来是一个非常简单的概念。它是包文件必须安装的目录。默认情况下，stow 目标目录被认为是从目录调用 stow 的目录。这种行为可以通过使用 `-t` 选项（ --target 的简写）轻松改变，这使我们可以指定一个替代目录。
### 一个实际的例子
我相信一个好的例子胜过 1000 句话，所以让我来展示 stow 如何工作。假设我们想编译并安装 `libx264`，首先我们克隆包含其源代码的仓库：
```
$ git clone git://git.videolan.org/x264.git
```
运行该命令几秒钟后，将创建 "x264" 目录，并且它将包含准备编译的源代码。我们切换到 "x264" 目录中并运行 `configure` 脚本，将 `--prefix` 指定为 /usr/local/stow/libx264 目录。
```
$ cd x264 && ./configure --prefix=/usr/local/stow/libx264
```
然后我们构建该程序并安装它：
```
$ make
# make install
```
x264 目录应该在 stow 目录内创建：它包含所有通常直接安装在系统中的东西。 现在，我们所要做的就是调用 stow。 我们必须从 stow 目录内运行这个命令，通过使用 `-d` 选项来手动指定 stow 目录的路径（默认为当前目录），或者通过如前所述用 `-t` 指定目标。我们还应该提供要作为参数存储的包的名称。 在这种情况下，我们从 stow 目录运行程序，所以我们需要输入的内容是：
```
# stow libx264
```
libx264 软件包中包含的所有文件和目录现在已经在调用 stow 的父目录 (/usr/local) 中进行了符号链接，因此，例如在 `/usr/local/ stow/x264/bin` 中包含的 libx264 二进制文件现在在 `/usr/local/bin` 中符号链接，`/usr/local/stow/x264/etc` 中的文件现在符号链接在 `/usr/local/etc` 中等等。通过这种方式，系统将显示文件已正常安装，并且我们可以容易地跟踪我们编译和安装的每个程序。要恢复该操作，我们只需使用 `-D` 选项：
```
# stow -d libx264
```
完成了！符号链接不再存在：我们只是“卸载”了一个 stow 包，使我们的系统保持在一个干净且一致的状态。 在这一点上，我们应该清楚为什么 stow 还用于管理 dotfiles。 通常的做法是在 git 仓库中包含用户特定的所有配置文件，以便轻松管理它们并使它们在任何地方都可用，然后使用 stow 将它们放在适当位置，如放在用户主目录中。
Stow 还会阻止你错误地覆盖文件：如果目标文件已经存在并且没有指向 Stow 目录中的包时，它将拒绝创建符号链接。 这种情况在 Stow 术语中称为冲突。
就是这样！有关选项的完整列表，请参阅 stow 帮助页，并且不要忘记在评论中告诉我们你对此的看法。
--------------------------------------------------------------------------------
via: https://linuxconfig.org/how-to-use-gnu-stow-to-manage-programs-installed-from-source-and-dotfiles
作者：[Egidio Docile][a]
译者：[MjSeven](https://github.com/MjSeven)
校对：[校对者ID](https://github.com/ 校对者ID)
本文由 [LCTT](https://github.com/LCTT/TranslateProject) 原创编译，[Linux中国](https://linux.cn/) 荣誉推出
[a]:https://linuxconfig.org