hasufell
/
portage-gentoo-git-config
1
0
Fork 0
Code Issues Pull Requests Releases Wiki Activity

Merge branch 'patch-1' of git://github.com/Maffblaster/portage-gentoo-git-config

This commit is contained in:
hasufell 2015-09-01 19:30:47 +02:00
parent a309c48677 0f5ecd64e9
commit 7b01671cd6
No known key found for this signature in database
GPG Key ID: 220CD1C5BDEED020
1 changed files with 9 additions and 8 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

17
README.md
View File

@ -1,15 +1,16 @@
This is not a full portage configuration. It contains only those parts that are
necessary to set up a gentoo github mirror based sync system:
* configures portage to sync via https://github.com/gentoo/gentoo.git
* updates metadata-cache (the first update might take long, all subsequent ones not)
* updates the dtd directory
* updates the glsa directory
* updates herds.xml
* updates the news directory
## Notes
* Configures Portage to sync via https://github.com/gentoo/gentoo.git URL.
* Updates metadata-cache (the first update might take long, all subsequent ones not).
* Updates the dtd directory.
* Updates the glsa directory.
* Updates `herds.xml` file.
* Updates the news directory.
Note that typically most repositories other than `gentoo` don't come with a pregenerated cache. It is a good idea to generate/update their cache every time they are synced. One way to do this, is by activating the `example` hook script that portage installs by default in /etc/portage/postsync.d:
## Notes ##
Note that typically most repositories other than `gentoo` don't come with a pregenerated cache. It is a good idea to generate/update their cache every time they are synced. One way to do this, is by activating the `example` hook script that portage installs by default in `/etc/portage/postsync.d`:
```
cp -i /etc/portage/repo.postsync.d/example /etc/portage/repo.postsync.d/gen_cache