1 |
On 11/21/14 18:14, Rich Freeman wrote: |
2 |
> On Fri, Nov 21, 2014 at 12:34 PM, James <wireless@×××××××××××.com> wrote: |
3 |
>> Here's one, very, very interesting proposals, under |
4 |
>> serious consideration: |
5 |
>> |
6 |
>> https://wiki.gentoo.org/wiki/Distributed_Gentoo |
7 |
>> |
8 |
>> |
9 |
>> I'd be curious what the fine and wonderful folks at |
10 |
>> gentoo_user think of this proposal. Old farts are |
11 |
>> welcome to comment, even encourage to "constructively rant".... |
12 |
> Honestly, I think it is a bit optimistic, though something I'd love to |
13 |
> see. I'm more of a fan of getting the new working before dismantling |
14 |
> the old, and I'm not keen on proposals that start out with gutting |
15 |
> what we already have before there is anything new to replace it. |
16 |
> Burning bridges usually isn't wise. |
17 |
> |
18 |
> The optimistic bit is that the proposal is that the only part of |
19 |
> Gentoo that would actually be developed centrally are the parts that |
20 |
> almost nobody is working on today. That basically amounts to just |
21 |
> having all the developers quit, and hoping that they all move on to |
22 |
> work on overlays instead of moving on to something else. |
23 |
> |
24 |
> There are a lot of technical challenges in such an approach - |
25 |
> supporting overlays isn't all that unlike trying to provide kernel |
26 |
> internal API stability. I think it could be done better, but it would |
27 |
> be a big change. IMHO it makes far more sense to make those changes |
28 |
> and use them for our own internal benefit in the main repository, and |
29 |
> THEN think about whether the main repository is still needed. |
30 |
> |
31 |
> -- |
32 |
> Rich |
33 |
> |
34 |
With regards to distributed gentoo; |
35 |
|
36 |
to me this sounds like gentoo already. Overlays / layman repositories. I |
37 |
even have my own overlay that is listed publicly for anybody to add: |
38 |
https://github.com/paigeadele/netcrave |
39 |
|
40 |
Which goes to say, the obvious should be assumed since anybody can have |
41 |
their own publicly listed overlay, you should know what's in it before |
42 |
you add it--it's a fairly autonomous system but you have to ask to get |
43 |
publicly to get your repo publicly list and If it were any easier, it |
44 |
would probably get abused. |
45 |
|
46 |
Technically you can even use git to manage your entire / filesystem if |
47 |
you want but it would be more productive to write your .gitignore to |
48 |
ignore all, then conditionally "un-ignore" things that need to be |
49 |
tracked thereafter. I did this but only for /etc because I've gotten |
50 |
tired of hunting down HOWTOs and more often than not a simple example is |
51 |
more than what I need to get stuff done: |
52 |
|
53 |
https://github.com/paigeadele/laptop.paigeat.info_etc/blob/master/.gitignore |
54 |
|
55 |
Honestly though I kinda wish I had done this from the top most |
56 |
directory, there are things here and there outside of /etc that I'd like |
57 |
to keep for reference or whatever reason. |
58 |
|
59 |
You can pretty much do whatever you want with gentoo, its up to you to |
60 |
decide whether or not to. |