public inbox for gentoo-dev@lists.gentoo.org
 help / color / mirror / Atom feed
From: Rich Freeman <rich0@gentoo.org>
To: gentoo-dev <gentoo-dev@lists.gentoo.org>
Subject: Re: [gentoo-dev] Vanilla sources
Date: Sat, 4 Jan 2020 07:54:07 -0500	[thread overview]
Message-ID: <CAGfcS_kxafwfFuV+n=SdgwSaGdBHapRnvotiDoStmgZuWHeHtA@mail.gmail.com> (raw)
In-Reply-To: <OXR3NLZA.SJ53EA2Z.7AJF3PQU@OPMY5W7L.Y2WPO3NT.QUGGKWDU>

On Sat, Jan 4, 2020 at 6:42 AM Roy Bamford <neddyseagoon@gentoo.org> wrote:
>
> On 2020.01.04 11:01, Rich Freeman wrote:
> >
> > Is there some reason that we should keep vanilla sources despite not
> > getting security handling?
> >
>
> Gentoo had this discussion before. The outcome was that
> vanilla-sources is just as Linus intended.
> If Gentoo did anything to it, it wouldn't be vanilla any longer.

Obviously.  I wasn't suggesting that we keep vanilla sources but not
make them vanilla.  That doesn't mean that they couldn't be
security-supported, or that we have to have them in the repo.

> Yes, it should be kept. We should not force users to learn
> git or tar.

Uh, all it does is install kernel sources.  They're useless unless you
build a kernel using them.

Apparently git and tar are too complicated for Gentoo users, but
managing symlinks, using make, managing a bootloader, dealing with the
kernel's configuration system, and so on are just fine?

I completely get the point of the distribution kernel project that was
just announced, as I already said.

> I agree git or a tarball of vanilla-sources is faster and more
> efficient but that's not a reason to drop it.
> By the same argument we could drop linux-firmware too.
> There are probably other packages that only install whatever
> they fetch. Could they be dropped?

So, a few issues with that argument:

1.  Those other packages are security supported.
2.  Those other packages are largely functional once installed, and to
the degree that they require configuration that is generally one-time
and after updates they remain functional.

All that said, it seems like vanilla-sources is pretty up-to-date, so
I'm not sure what we mean by it not being security supported.  I just
took that as a given.  Does that mean that we're not releasing patches
before upstream?  If so, that seems like a pretty minor issue since
upstream generally does security bumps pretty quickly.  4.4.208 isn't
in our repo but was released today - I'm not sure how quickly these
get bumped.  If our repo could be days behind that is definitely
another reason not to host this stuff, as users should be directed
upstream if our packages aren't security supported.

On a further aside, I just noticed how up-to-date gentoo-sources are.
Kudos to whoever is doing that these days - for a while it was tending
to slip a bit but it seems like we're basically current.

-- 
Rich


  reply	other threads:[~2020-01-04 12:54 UTC|newest]

Thread overview: 50+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-12-28  7:09 [gentoo-dev] Keywordreqs and slacking arch teams Michał Górny
2019-12-28  9:27 ` Kent Fredric
2019-12-28  9:35   ` Fabian Groffen
2019-12-28 11:05     ` Kent Fredric
2019-12-28 11:14       ` Michael 'veremitz' Everitt
2019-12-28 11:27         ` Kent Fredric
2019-12-28 11:40           ` James Le Cuirot
2019-12-28 11:44             ` Kent Fredric
2019-12-28 11:32         ` Kent Fredric
2019-12-28 11:35           ` Michael 'veremitz' Everitt
2019-12-28 11:42             ` Kent Fredric
2019-12-28 18:05               ` Alec Warner
2019-12-29  2:19                 ` Aaron Bauman
2019-12-29  5:09                   ` Kent Fredric
2019-12-30  1:45         ` A Schenck
2020-01-02 20:32       ` Rolf Eike Beer
2020-01-02 23:25         ` Mike Pagano
2020-01-02 23:35           ` Rolf Eike Beer
2020-01-03  0:19             ` Michael 'veremitz' Everitt
2020-01-03  2:40             ` Aaron Bauman
2020-01-03 10:00               ` Rolf Eike Beer
2020-01-04 11:09                 ` Rolf Eike Beer
2020-01-04 11:25                   ` Michael 'veremitz' Everitt
2020-01-04 13:35                     ` Rolf Eike Beer
2020-01-03 14:37             ` [gentoo-dev] Vanilla sources Michael Orlitzky
2020-01-03 14:40               ` Toralf Förster
2020-01-03 14:41                 ` Michael Orlitzky
2020-01-03 14:46                   ` Rich Freeman
2020-01-03 14:48                     ` Toralf Förster
2020-01-03 22:32                       ` Michael 'veremitz' Everitt
2020-01-04  7:38                       ` Hanno Böck
2020-01-04 18:39                         ` William Hubbs
2020-01-04 18:41                         ` Michał Górny
2020-01-07  8:52                           ` Hanno Böck
2020-01-03 14:52                     ` Michael Orlitzky
2020-01-03 14:55                       ` Michael Orlitzky
2020-01-03 16:28                         ` Aaron Bauman
2020-01-04 11:01                           ` Rich Freeman
2020-01-04 11:42                             ` Roy Bamford
2020-01-04 12:54                               ` Rich Freeman [this message]
2020-01-04 13:08                                 ` Roy Bamford
2020-01-04 13:43                                   ` Thomas Deutschmann
2020-01-05 10:34                                     ` Roy Bamford
2020-01-04 20:13                                 ` Christopher Head
2020-01-04 20:39                                   ` Rich Freeman
2020-01-04 13:47                             ` Thomas Deutschmann
2020-01-04 18:41                         ` William Hubbs
2020-01-04 18:42                           ` Michał Górny
2020-01-04 19:13                           ` Rolf Eike Beer
2020-01-05 16:41                             ` Michael Orlitzky

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_kxafwfFuV+n=SdgwSaGdBHapRnvotiDoStmgZuWHeHtA@mail.gmail.com' \
    --to=rich0@gentoo.org \
    --cc=gentoo-dev@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