moparisthebest
/
pacman
mirror of https://github.com/moparisthebest/pacman
1
0
Fork 0
Code Issues Releases Wiki Activity

Fix minor grammatical issues in doc/index.txt 

Signed-off-by: Jason St. John <jstjohn@purdue.edu>
Signed-off-by: Allan McRae <allan@archlinux.org>
This commit is contained in:
Jason St. John 2013-11-07 23:26:19 -05:00 committed by Allan McRae
parent d78f45ae0c
commit b7b3f9c5e7
1 changed files with 8 additions and 8 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

16
doc/index.txt
View File

@ -21,22 +21,22 @@ option) with a master server through the use of package databases. Prior to
this, packages would have to be installed manually using the '\--add' and this, packages would have to be installed manually using the '\--add' and
'\--upgrade' operations. '\--upgrade' operations.
Version 3.0 was the switch to a two-part pacman- a backend named libalpm Version 3.0 was the switch to a two-part pacman -- a back-end named libalpm
(library for Arch Linux Package Management), and the familiar pacman frontend. (library for Arch Linux Package Management) and the familiar pacman front-end.
Speed in many cases was improved, along with dependency and conflict resolution Speed in many cases was improved, along with dependency and conflict resolution
being able to handle a much wider variety of cases. The switch to a being able to handle a much wider variety of cases. The switch to a
library-based program should also make it easier in the future to develop library-based program should also make it easier in the future to develop
alternative front ends. alternative front ends.
Version 4.0 added package signing and verification capabilities to the entire Version 4.0 added package signing and verification capabilities to the entire
makepkg/repo-add/pacman toolchain via GNUPG and GPGME. makepkg/repo-add/pacman toolchain via GnuPG and GPGME.
Documentation Documentation
------------- -------------
Manpages Man Pages
~~~~~~~~ ~~~~~~~~~
There are several manpages available for the programs, utilities, and There are several man pages available for the programs, utilities, and
configuration files dealing with pacman. configuration files dealing with pacman.
* linkman:PKGBUILD[5] * linkman:PKGBUILD[5]
@ -194,7 +194,7 @@ link:https://mailman.archlinux.org/pipermail/pacman-dev/[view the archives].
Source Code Source Code
~~~~~~~~~~~ ~~~~~~~~~~~
Development of pacman is currently done in GIT. The central repository is Development of pacman is currently done in Git. The central repository is
hosted by Arch Linux, although some of the developers have their own trees (ask hosted by Arch Linux, although some of the developers have their own trees (ask
on the above mailing lists if you are interested in finding the locations of on the above mailing lists if you are interested in finding the locations of
these trees). these trees).
@ -238,7 +238,7 @@ Bugs
---- ----
If you find bugs (which is quite likely), please email them to the pacman-dev If you find bugs (which is quite likely), please email them to the pacman-dev
mailing last at mailto:pacman-dev@archlinux.org[] with specific information mailing last at mailto:pacman-dev@archlinux.org[] with specific information
such as your commandline, the nature of the bug, and even the package database such as your command-line, the nature of the bug, and even the package database
if it helps. if it helps.
You can also post a bug to the Arch Linux bug tracker You can also post a bug to the Arch Linux bug tracker