public inbox for gentoo-project@lists.gentoo.org
 help / color / mirror / Atom feed
From: Alec Warner <antarus@gentoo.org>
To: gentoo-project <gentoo-project@lists.gentoo.org>
Subject: Re: [gentoo-project] Repo mirror & CI: official statement wrt GitHub
Date: Thu, 14 Jun 2018 22:16:46 -0400	[thread overview]
Message-ID: <CAAr7Pr_kC9p4HLWwaTUOcvvw4d4xv0yE6+D8PMYzdWrCUQOn+Q@mail.gmail.com> (raw)
In-Reply-To: <e6a98094-876f-b11d-f6b1-e6abe7061e1e@gentoo.org>

[-- Attachment #1: Type: text/plain, Size: 2142 bytes --]

On Thu, Jun 14, 2018 at 8:33 PM, Thomas Deutschmann <whissi@gentoo.org>
wrote:

> On 2018-06-14 16:14, Alec Warner wrote:
> > They seem to offer docker packages, so we could just nab those and run
> > them in containers on hosts. I'm not too keen on doing a bunch of
> > (really what I consider busywork) to try to 'get it working on Gentoo.'
> > We already use upstream provided containers and I expect that to
> > continue as upstreams continue to abandon the 'release packages' model
> > and move to 'release sets of containers' model.
>
> Huh? Is this the Gentoo-way? I hope not! :(
>
> No, I really hope something like that will never happen. Like I hope we
> will never see the attempt to add "FLATPAK", "Snap"... to the official
> Gentoo repository.
>

I think you will find that vendors who offer fairly complex applications
will continue to focus on vertically integrated solutions
(e.g. containers) because its cheaper (build once run anywhere) and
scalable (you don't need to maintain N packages, for N distros.)

I won't comment on what the "Gentoo" way is (because there are dozens of us
and we don't all agree) but as a human trying to deploy these sorts of
services; I don't see much point in packaging them when upstream offers a
container deployment. Given the dozens of hours I could spend trying to
write ebuilds for all of the bundled stuff vs deploying the container..I'm
going to deploy the container most of the time precisely because I don't
need the 'gentoo customized build', particularly when containers offer
isolation boundaries between the application runtime and my system runtime.

Obviously containers have their own customization challenges (but also
provide layers of isolation where extreme customization is lower priority
than 10 years ago) and also present interesting security challenges (how do
you keep up to date, you cannot use more traditional security tools) but I
suspect organizations can adapt to the former and the industry will provide
for the latter at some point.

-A


>
> --
> Regards,
> Thomas Deutschmann / Gentoo Linux Developer
> C4DD 695F A713 8F24 2AA1 5638 5849 7EE5 1D5D 74A5
>
>

[-- Attachment #2: Type: text/html, Size: 2916 bytes --]

  parent reply	other threads:[~2018-06-15  2:16 UTC|newest]

Thread overview: 28+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-06-09  7:25 [gentoo-project] Repo mirror & CI: official statement wrt GitHub Michał Górny
2018-06-09  7:50 ` Ulrich Mueller
2018-06-09  7:52   ` Michał Górny
2018-06-09  9:11     ` Thomas Deutschmann
2018-06-11 12:15     ` Kristian Fiskerstrand
2018-06-11 13:28     ` Rich Freeman
2018-06-14  9:47       ` James Le Cuirot
2018-06-14 14:14         ` Alec Warner
2018-06-14 14:25           ` Mauricio Lima Pilla
2018-06-15  0:33           ` Thomas Deutschmann
2018-06-15  1:14             ` Aaron W. Swenson
2018-06-15  2:16             ` Alec Warner [this message]
2018-06-15  7:20               ` Kristian Fiskerstrand
2018-06-16 23:55               ` Virgil Dupras
2018-06-17  0:25                 ` Rich Freeman
2018-06-16 21:58           ` Andreas K. Huettel
2018-06-16 23:14             ` Rich Freeman
2018-06-16 23:45             ` Alec Warner
2018-06-17  1:05               ` Brian Dolbec
2018-06-14 19:55 ` kuzetsa
2018-06-15  0:26   ` Thomas Deutschmann
2018-06-15  2:27     ` kuzetsa
2018-06-15 11:50       ` Thomas Deutschmann
2018-06-15 14:55         ` kuzetsa
2018-06-15 15:31           ` Rich Freeman
2018-06-15 16:03             ` kuzetsa
2018-06-15 16:11               ` Rich Freeman
2018-06-15 16:22                 ` kuzetsa

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=CAAr7Pr_kC9p4HLWwaTUOcvvw4d4xv0yE6+D8PMYzdWrCUQOn+Q@mail.gmail.com \
    --to=antarus@gentoo.org \
    --cc=gentoo-project@lists.gentoo.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox