From: Rich Freeman <rich0@gentoo.org>
To: gentoo-project <gentoo-project@lists.gentoo.org>
Cc: Alec Warner <antarus@gentoo.org>
Subject: Re: [gentoo-project] Repo mirror & CI: official statement wrt GitHub
Date: Sat, 16 Jun 2018 19:14:45 -0400 [thread overview]
Message-ID: <CAGfcS_mdkw_YuO3Z1BXMxgRY7w=A6ZX0Ad4ZEoGsMwjUfaN4XQ@mail.gmail.com> (raw)
In-Reply-To: <1685513.lPs1pTU4bp@pinacolada>
On Sat, Jun 16, 2018 at 5:58 PM Andreas K. Huettel <dilfridge@gentoo.org> wrote:
>
> So I'd suggest we either are convinced that our packaging actually makes
> sense, and use it, or we close shop.
>
Perhaps it makes more sense for linked binaries than for scripts or
java (ie, 99% of web hosting)?
In any case, the solution we're using today is Github, which also
doesn't run on Gentoo and is proprietary, because nobody can be
bothered to deal with getting Gitlab to run on Gentoo. It seems like
at least moving to something that could conceivably be self-hosted on
any distro (perhaps even Gentoo) would be an improvement.
However, as others have pointed out Gitlab apparently needs fairly
frequent updates. So, it is something that would require a bit of
care. That would be an argument for hosting it on an
upstream-recommended platform that actually gets updates if we want to
host it ourselves. If we had a long line of people willing to keep
everything up to date on Gentoo that would be one thing, but right now
it isn't even packaged, which doesn't speak well for rapid security
updates.
I guess in the meantime we can just stick with Github...
--
Rich
next prev parent reply other threads:[~2018-06-16 23:15 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 [this message]
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='CAGfcS_mdkw_YuO3Z1BXMxgRY7w=A6ZX0Ad4ZEoGsMwjUfaN4XQ@mail.gmail.com' \
--to=rich0@gentoo.org \
--cc=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