diff options
| author | http://www.rowanthorpe.com/ <http://www.rowanthorpe.com/@web> | 2010-04-12 02:07:35 +0000 |
|---|---|---|
| committer | GNU Hurd web pages engine <web-hurd@gnu.org> | 2010-04-12 02:07:35 +0000 |
| commit | f0e7992f170aa03e5f4e2b364071d1308bbc0574 (patch) | |
| tree | 245931f5d0e84a420f65bd43b09df674218a70b7 /hurd/running/gnu/universal_package_manager.mdwn | |
| parent | 84bc73315b5b4816592b00caae68cf36e24ee563 (diff) | |
scattered small typo/grammar fixes
Diffstat (limited to 'hurd/running/gnu/universal_package_manager.mdwn')
| -rw-r--r-- | hurd/running/gnu/universal_package_manager.mdwn | 14 |
1 files changed, 7 insertions, 7 deletions
diff --git a/hurd/running/gnu/universal_package_manager.mdwn b/hurd/running/gnu/universal_package_manager.mdwn index 74c1ac8b..6dca1b24 100644 --- a/hurd/running/gnu/universal_package_manager.mdwn +++ b/hurd/running/gnu/universal_package_manager.mdwn @@ -20,10 +20,10 @@ Basically all package management schemes follow similar approach, it will have a There can be both aproaches - * Re-implement rpm, dpkg... to recognise stow as backend instead of its own data store. In that case we will have to re implement, apt-rpm, yum ... - * Implement a translator which reads stow and show it as an rpm data store for yum, deb data store for apt-get ... + * Re-implement rpm, dpkg... to recognise stow as backend instead of its own data store. In that case we will have to re-implement, apt-rpm, yum ... + * Implement a translator which reads stow and show it as an rpm data store for yum, deb data store for apt-get ... -One goal is obviously choice of packaging and hence availability of more packages. Also this gives maintainers a chioce to continue builing packages for GNU in the format they are already familiar with. The second goal is to demonstrate the flexibility GNU offers in implementing functionality in filesystems (open/read/write interface). +One goal is obviously choice of packaging and hence availability of more packages. Also this gives maintainers a choice to continue building packages for GNU in the format they are already familiar with. The second goal is to demonstrate the flexibility GNU offers in implementing functionality in filesystems (open/read/write interface). ## Why? @@ -40,7 +40,7 @@ With the increased flexibility in implementing filesystems as per the requiremen ## How? - * Installtion of a package is just drag the pacakage (be it a tgz, rpm, deb or an exe) and drop it to the package manager. + * Installation of a package is just drag the package (be it a tgz, rpm, deb or an exe) and drop it to the package manager. * apt-cache search vim --> ls -al /packages/meta/ |grep vim * apt-get install vim --> install vim @@ -77,12 +77,12 @@ just writing the new translator. ## Initial idea -A bit complex than the earlier scheme but it is more exciting and we can look at this schem seriously once we have the simple scheme working. +A bit more complex than the earlier scheme but it is more exciting and we can look at this scheme seriously once we have the simple scheme working. All packages are installed at `/packages/binary/<packagename>/<packageversion>`. -For eaxmple vim 6.4 version can be installed from source like +For example vim 6.4 version can be installed from source like # cd vim64 # ./configure --prefix=/packages/binary/vim/6.4 @@ -99,7 +99,7 @@ Now if you have another vim version, say 7.0 then just follow the steps # make # make install -You have 2 versions of vim and how can you sepcify which one is the current version? You can symlink the current version to select the version you would like to see as default +You have 2 versions of vim and how can you specify which one is the current version? You can symlink the current version to select the version you would like to see as default # ln -s /packages/binary/vim/7.0 /packages/vim/current |