My two cents worth, I think broader features not necessarily better; to draw an analogy, dotGo 2015 - Rob Pike - Simplicity is Complicated <https://www.youtube.com/watch?v=rFejpH_tAHM>, ".. a lot of people talk about tooling... but the real reason [that the go language is sucessful] is simplicity..most of the [other languages keep adding] new features..javascript gets classes.. I realised.. that all of these languages are changing into the same language"... and more, but interesting nonetheless.
I am opinionated, I have come to Gentoo because I rejected what I saw as increased abstraction and concepts being piled onto other distributions, ironically with such features diminishing rather than expanding choices. So what would be more powerful? IMHO patience and more concentration on current build tools in the short term at least, back the current product and skills within this existing platform, for now. Why? because it is a good platform, patchy perhaps in some areas, but too good to throw away and this product is in a perfect position to continue to encouraging community involvement and improvement against the current toolset. Jumping on, or dissapating current work across big changes to build concepts, will harm the product at least in the short term. Long term, let the law of commits decide. Kind regards, On Fri, Nov 10, 2017 at 9:03 AM, Samuel Bernardo < [email protected]> wrote: > Hi, > > I send this email to know the devs opinion about Gentoo integration with > Open Build Service[1]. > > When creating specialized images and using an automated process for > testing before deployment, I think that Open Build Service would be > useful. It already support all major binary based distros and I think > that Gentoo could be in there also. > > There is also a subforum with some interesting posts[2], where was > mentioned some references for Gentoo@OBS. > > I reviewed catalyst scripts and Gentoo workflow when creating the > package repository, and I think that it could be integrated in OBS. The > advantage is about creating repositories of binary packages from Gentoo > that would be used to deploy containers or VMs. This way, updates could > be applied to the images. OBS will be responsible to compile all images > that would be associated with their own created binary repository. > > To use the binary repository in Gentoo is suggested to use a nfs share > for portage/packages directory[3], but it would be a smoother > integration if emerge gets the packages directly from an url. > > You can ask, but for that why not using a binary disto? Well they're not > Gentoo... What I mean with this is that all the Gentoo tools, portage > architecture and the ebuild format that allows for excellent source > package definition (EAPI), turn it unique. Also the freedom associated > with Gentoo distribution that, with less effort than the others, allows > for the creation of new distros. Cross compiling tools are also amazing. > > So why shouldn't I wish to use Gentoo always? > > Well it don't need to be OBS, but since this opensource project have > some nice ideas, why not starting from there? > > Best, > > Samuel > > [1] http://openbuildservice.org/ > > [2] https://forums.gentoo.org/viewtopic-p-7829060.html > > [3] https://wiki.gentoo.org/wiki/Binary_package_guide > > >
