| Arch Linux Installation Guide |
|
|
|
| Written by axel | |
|
Page 17 of 20
II-3 Local RepositoryPreviously, the creation of a local repository was needed, which is very useful. As long as the substructure exists, lets see how we can handle it. Firstly, lets see how the packets of Arch are named and how they should be named: <program>-<version>-<packet revision>-<architecture>.pkg.tar.gz
for amd64 x86_64
i686
program: gimageview The packet will be named, depending on the architecture for which it is designed: for amd64 gimageview-0.2.27-4-x86_64.pkg.tar.gz
gimageview-0.2.27-4-i686.pkg.tar.gz
All these files should be placed on the packages directory we have created before on our local repository. For example: for amd64 /mnt/repos/arch-local/amd64/custom/packages/
/mnt/repos/arch-local/x86/custom/packages/
PKGBUILD
for amd64 /mnt/repos/arch-local/amd64/custom/list/
/mnt/repos/arch-local/x86/custom/list/
<program>-<version>-<packet revision>
for amd64 /mnt/repos/arch-local/amd64/custom/list/gimageview-0.2.27-4/ for x86 /mnt/repos/arch-local/x86/custom/list/gimageview-0.2.27-4/ and place there its PKGBUILD. Concluding, things are simple:
- Deleting packet from local repository
- Adding packet from local repository
- Renewal of the packet with a new version While finished, dont forget to run once ti update script: update-local-repo custom amd64
update-local-repo custom x86
pacman -Sy
|
|
| Last Updated ( Sunday, 26 October 2008 ) |
| < Prev | Next > |
|---|






