1 |
W dniu nie, 08.07.2018 o godzinie 11∶57 -0700, użytkownik Zac Medico |
2 |
napisał: |
3 |
> On 07/08/2018 11:42 AM, Michał Górny wrote: |
4 |
> > W dniu nie, 08.07.2018 o godzinie 11∶04 -0700, użytkownik Zac Medico |
5 |
> > napisał: |
6 |
> > > On 07/08/2018 06:56 AM, Michał Górny wrote: |
7 |
> > > > W dniu nie, 08.07.2018 o godzinie 15∶02 +0200, użytkownik Kristian |
8 |
> > > > Fiskerstrand napisał: |
9 |
> > > > > On 07/08/2018 08:53 AM, Michał Górny wrote: |
10 |
> > > > > > Is safe git syncing implemented already? If not, maybe finish it first and cover both with a single news item. Git is going to be more efficient here, so people may want to learn they have an alternative. |
11 |
> > > > > |
12 |
> > > > > Why complicate things, and increase wait for something that benefits |
13 |
> > > > > most users, just to give alternatives to a few using non-default sync |
14 |
> > > > > mechanism. Securing git distribution is a whole different ballpark. |
15 |
> > > > > |
16 |
> > > > |
17 |
> > > > Let me rephrase. Let's say I'm using rsync. This new feature is |
18 |
> > > > something positive but it breaks my use case (for one of the listed |
19 |
> > > > reasons -- overlayfs, inode use, small fs cache). After reading this |
20 |
> > > > news item, I learn that my only option is to disable the new feature. |
21 |
> > > > |
22 |
> > > > Now, I would appreciate being told that there's an alternate sync method |
23 |
> > > > that handles secure updates without having all those drawbacks. |
24 |
> > > |
25 |
> > > The thing is, the normal git tree doesn't even provide pre-generated |
26 |
> > > metadata, and I see then gentoo-mirror repo that provides metadata does |
27 |
> > > not have commits signed with an release key: |
28 |
> > > |
29 |
> > > https://github.com/gentoo-mirror/gentoo/commits/stable |
30 |
> > > |
31 |
> > > So I'm really not comfortable recommending git to anyone at this point. |
32 |
> > |
33 |
> > Wrong twice. |
34 |
> > |
35 |
> > Firstly, the canonical URL is: |
36 |
> > |
37 |
> > https://anongit.gentoo.org/git/repo/sync/gentoo.git |
38 |
> > (https://gitweb.gentoo.org/repo/sync/gentoo.git) |
39 |
> > |
40 |
> > Secondly, the merge commits (i.e. top commits that are verified |
41 |
> > by Portage) are signed by dedicated key that is part of the infra key |
42 |
> > set. In other words, it works out of the box. |
43 |
> |
44 |
> Is there any documentation that shows users how to migrate to git, and |
45 |
> what the pros and cons might be? Maybe its worthy of its own news item. |
46 |
|
47 |
Maybe. I don't really know, and don't think it's a good idea to show 30 |
48 |
news item of things users might like on every new Gentoo install. |
49 |
|
50 |
-- |
51 |
Best regards, |
52 |
Michał Górny |