The Unix Heritage Society mailing list
 help / color / mirror / Atom feed
From: imp@bsdimp.com (Warner Losh)
Subject: [TUHS] Why BSD didn't catch on more, and Linux did
Date: Tue, 6 Feb 2018 15:44:08 -0700	[thread overview]
Message-ID: <CANCZdfp=vxXXPjUgnPZw1uNc+nj1cED5wx-=u7BpCrvyXCW3iA@mail.gmail.com> (raw)
In-Reply-To: <CAGGBd_r3K9kPvuHuCavzaX6ZS8qh0wMpYwOFA4rPNOoK7XJFLw@mail.gmail.com>

On Tue, Feb 6, 2018 at 3:13 PM, Dan Stromberg <drsalists at gmail.com> wrote:

> 5) I think FreeBSD's ports and similar huge-source-tree approaches
> didn't work out as well Linux developers contributing their changes
> upstream.
>

I think you confuse what ports was supposed to do. It was supposed to be
"make these patches NOW to make the software available to users" paired
with "submit the patches upstream to ease future support burdens". But the
latter didn't happen often enough at times, especially as people moved on
from the FreeBSD project and complex software became unsupported. It's
really no different than what all the distributions have to do on Linux,
but had a different bias for forcing the question than FreeBSD did in the
early days. That's largely changed, and has mostly worked out....

The bigger issue with 'large trees' is that there was no convenient, binary
packaged way to subset. Having everything in one tree avoids much of the
version chasing that you have with Linux packages that the package set
maintainers have to grapple with...

Warner
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://minnie.tuhs.org/pipermail/tuhs/attachments/20180206/f0a1a3a5/attachment.html>


  parent reply	other threads:[~2018-02-06 22:44 UTC|newest]

Thread overview: 33+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-02-06 22:13 Dan Stromberg
2018-02-06 22:38 ` Clem Cole
2018-02-06 22:44 ` Warner Losh [this message]
2018-02-06 22:59   ` Pete Wright
2018-02-06 22:59 ` Derek Fawcus
2018-02-07  1:14   ` Dave Horsfall
2018-02-06 23:02 ` Theodore Ts'o
2018-02-07  0:22   ` Andy Kosela
2018-02-07  1:02     ` Robert Brockway
2018-02-07  3:47       ` George Michaelson
2018-02-07  1:29   ` Clem Cole
2018-02-07 15:13     ` Theodore Ts'o
2018-02-07 16:59       ` Jon Forrest
2018-02-07 17:27       ` Clem Cole
2018-02-07 19:21         ` Dan Cross
2018-02-07 21:24           ` Clem Cole
2018-02-07 19:31         ` Nemo
2018-02-07 19:49         ` Theodore Ts'o
2018-02-07 19:53           ` Dan Cross
2018-02-07 20:26             ` Theodore Ts'o
2018-02-07 21:06               ` Clem Cole
2018-02-07 21:31               ` Clem Cole
2018-02-07 17:52       ` Tom Ivar Helbekkmo
2018-02-07  8:04   ` Tom Ivar Helbekkmo
2018-02-07  8:51   ` Arrigo Triulzi
2018-02-07  8:27 ` Wesley Parish
2018-02-07  8:39   ` emanuel stiebler
2018-02-07 10:44     ` Arrigo Triulzi
2018-02-07 13:14   ` Chet Ramey
2018-02-07 14:42   ` Nemo
2018-02-09  2:53     ` Wesley Parish
2018-02-11 20:22       ` Derek Fawcus
2018-02-12  0:31         ` Robert Brockway

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='CANCZdfp=vxXXPjUgnPZw1uNc+nj1cED5wx-=u7BpCrvyXCW3iA@mail.gmail.com' \
    --to=imp@bsdimp.com \
    /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;
as well as URLs for NNTP newsgroup(s).