README updates.
Excellent work hasufell!
This commit is contained in:
parent
8d7caaa54c
commit
0f5ecd64e9
17
README.md
17
README.md
@ -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
|
||||
|
Loading…
Reference in New Issue
Block a user