| 1 |
On Sun, Jul 30, 2017 at 12:27 PM, Ian Zimmerman <itz@××××××××××××.org> wrote: |
| 2 |
> On 2017-07-29 06:25, Rich Freeman wrote: |
| 3 |
> |
| 4 |
>> IMO unless you really need to read them offline it is probably just as |
| 5 |
>> easy to just browse the git repository. I find github provides the |
| 6 |
>> nicest viewer |
| 7 |
> |
| 8 |
> But which one? There is gentoo/gentoo _and_ gentoo-mirror/gentoo. TBH |
| 9 |
> the existence of both doesn't give me a warm & fuzzy feeling. |
| 10 |
> |
| 11 |
|
| 12 |
Git is a distributed vcs, so there are lots of copies floating around. |
| 13 |
Both should give you the same history for anything you actually care |
| 14 |
about. The first is just a clone of the official Gentoo repository. |
| 15 |
The second adds metadata to it, so it will have the same history with |
| 16 |
some delay, but with an extra commit adding all the metadata to it. |
| 17 |
The first is best for submitting pull requests. The second is best |
| 18 |
for syncing /usr/portage from as it: |
| 19 |
|
| 20 |
1. Contains pre-built metadata (like the rsync mirrors), which means |
| 21 |
emerge will run faster. It isn't absolutely essential since emerge |
| 22 |
will just build it on the fly if it has to, but it is slower. |
| 23 |
2. The default stable branch does a repoman QA check before pulling |
| 24 |
which means that if a dev makes an obvious error it pauses the |
| 25 |
repository until it is fixed. So, if you sync from this you won't |
| 26 |
errors like your stable system trying to pull in an unstable |
| 27 |
dependency, which usually go away if you re-sync because by then the |
| 28 |
dev in question has usually been beaten back into submission. The |
| 29 |
most recent commit is guaranteed to pass the automated QA checks at |
| 30 |
least. |
| 31 |
|
| 32 |
Other than the gentoo-mirror one being a little behind (or more behind |
| 33 |
if a dev did cause a QA issue), the histories are going to be the |
| 34 |
same. |
| 35 |
|
| 36 |
-- |
| 37 |
Rich |
Archives