1 |
My two cents worth, |
2 |
|
3 |
I think broader features not necessarily better; to draw an analogy, dotGo |
4 |
2015 - Rob Pike - Simplicity is Complicated |
5 |
<https://www.youtube.com/watch?v=rFejpH_tAHM>, ".. a lot of people talk |
6 |
about tooling... but the real reason [that the go language is sucessful] is |
7 |
simplicity..most of the [other languages keep adding] new |
8 |
features..javascript gets classes.. I realised.. that all of these |
9 |
languages are changing into the same language"... and more, but interesting |
10 |
nonetheless. |
11 |
|
12 |
I am opinionated, I have come to Gentoo because I rejected what I saw as |
13 |
increased abstraction and concepts being piled onto other distributions, |
14 |
ironically with such features diminishing rather than expanding choices. So |
15 |
what would be more powerful? IMHO patience and more concentration on |
16 |
current build tools in the short term at least, back the current product |
17 |
and skills within this existing platform, for now. Why? because it is a |
18 |
good platform, patchy perhaps in some areas, but too good to throw away and |
19 |
this product is in a perfect position to continue to encouraging community |
20 |
involvement and improvement against the current toolset. Jumping on, or |
21 |
dissapating current work across big changes to build concepts, will harm |
22 |
the product at least in the short term. Long term, let the law of commits |
23 |
decide. |
24 |
|
25 |
Kind regards, |
26 |
|
27 |
|
28 |
|
29 |
On Fri, Nov 10, 2017 at 9:03 AM, Samuel Bernardo < |
30 |
samuelbernardo.mail@×××××.com> wrote: |
31 |
|
32 |
> Hi, |
33 |
> |
34 |
> I send this email to know the devs opinion about Gentoo integration with |
35 |
> Open Build Service[1]. |
36 |
> |
37 |
> When creating specialized images and using an automated process for |
38 |
> testing before deployment, I think that Open Build Service would be |
39 |
> useful. It already support all major binary based distros and I think |
40 |
> that Gentoo could be in there also. |
41 |
> |
42 |
> There is also a subforum with some interesting posts[2], where was |
43 |
> mentioned some references for Gentoo@OBS. |
44 |
> |
45 |
> I reviewed catalyst scripts and Gentoo workflow when creating the |
46 |
> package repository, and I think that it could be integrated in OBS. The |
47 |
> advantage is about creating repositories of binary packages from Gentoo |
48 |
> that would be used to deploy containers or VMs. This way, updates could |
49 |
> be applied to the images. OBS will be responsible to compile all images |
50 |
> that would be associated with their own created binary repository. |
51 |
> |
52 |
> To use the binary repository in Gentoo is suggested to use a nfs share |
53 |
> for portage/packages directory[3], but it would be a smoother |
54 |
> integration if emerge gets the packages directly from an url. |
55 |
> |
56 |
> You can ask, but for that why not using a binary disto? Well they're not |
57 |
> Gentoo... What I mean with this is that all the Gentoo tools, portage |
58 |
> architecture and the ebuild format that allows for excellent source |
59 |
> package definition (EAPI), turn it unique. Also the freedom associated |
60 |
> with Gentoo distribution that, with less effort than the others, allows |
61 |
> for the creation of new distros. Cross compiling tools are also amazing. |
62 |
> |
63 |
> So why shouldn't I wish to use Gentoo always? |
64 |
> |
65 |
> Well it don't need to be OBS, but since this opensource project have |
66 |
> some nice ideas, why not starting from there? |
67 |
> |
68 |
> Best, |
69 |
> |
70 |
> Samuel |
71 |
> |
72 |
> [1] http://openbuildservice.org/ |
73 |
> |
74 |
> [2] https://forums.gentoo.org/viewtopic-p-7829060.html |
75 |
> |
76 |
> [3] https://wiki.gentoo.org/wiki/Binary_package_guide |
77 |
> |
78 |
> |
79 |
> |