public inbox for gentoo-project@lists.gentoo.org
 help / color / mirror / Atom feed
From: Brian Dolbec <dolsen@gentoo.org>
To: gentoo-project@lists.gentoo.org
Subject: Re: [gentoo-project] Repo mirror & CI: official statement wrt GitHub
Date: Sat, 16 Jun 2018 18:05:42 -0700	[thread overview]
Message-ID: <20180616180542.6be739a5@professor-x> (raw)
In-Reply-To: <CAAr7Pr9r8LHWRvEjq1-axCPe_3JdLt=f6oZqJsdK+qqN8LTRPA@mail.gmail.com>

On Sat, 16 Jun 2018 19:45:18 -0400
Alec Warner <antarus@gentoo.org> wrote:

> On Sat, Jun 16, 2018 at 5:58 PM, Andreas K. Huettel
> <dilfridge@gentoo.org> wrote:
> 
> > Am Donnerstag, 14. Juni 2018, 16:14:48 CEST schrieb Alec Warner:
> >  
> > > 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.
> > >
> > > -A  
> >
> > Apart from all the implications that have already been brought up,
> > that's
> >
> > 1) a public relations nightmare waiting to happen
> > (future discussion: "Err, wait, central Gentoo infrastructure runs
> > on an Ubuntu-based container? Well, then we switch directly to
> > Ubuntu.") 
> 
> Its unclear what the upstream containers might be based on. CoreOS or
> Alpine Linux are both common bases (and CoreOS is ironically a
> Gentoo-powered[1] distro using our tree and tools.) I'm not sure
> people would switch because of that.
> 
> 

Except that Red-Hat just bought CoreOS and are intending to replace the
Gentoo base with Red-Hat.  (Reported by one of my co-workers that just
attended the big docker conference and at least one of the talks where
that was discussed)




-- 
Brian Dolbec <dolsen>



  reply	other threads:[~2018-06-17  1:05 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
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 [this message]
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=20180616180542.6be739a5@professor-x \
    --to=dolsen@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