Re: Fwd: Unified BSD?

[Martin <martin.kelly4000%gmail.com@localhost>]

Sorry forget that last message.

GNOME was a bad example, but you did in essence you clarify my point. That FreeBSD or whichever one you talk about may or may not be using a different pkgsrc branch.

I didn't call any components standardized, i said even if you were to standardize certain components for all BSDs (related to package management/ source) you still would have to get around the fact that each of them may use a different pkgsrc branch.

Otherwise you wouldn't have the current differences in software compatibility where FreeBSD has what (28000 packages?) and NetBSD has (15000?)

On Wed, Dec 5, 2012 at 1:54 AM, Martin <martin.kelly4000%gmail.com@localhost> wrote:

I understand that, what your not getting is that i am talking about the release schedule of the individual BSD distros not the release schedule of pkgsrc.

On Tue, Dec 4, 2012 at 7:02 PM, John Marino <netbsd%marino.st@localhost> wrote:

On 12/4/2012 07:14, Aleksej Saushev wrote:

Martin<martin.kelly4000@gmail.com>  writes:

I can see how you could misunderstand what i said.

My point was about that each of the BSD's use pkgsrc in a different way and
the releases from FreeBSD, NetBSD, OpenBSD or DflyBSD don't all rely on the
exact same packages for every release (i.e. NetBSD 6 and FreeBSD 9 do not
use the same version of GNOME-2 desktop; poor example), and that generally
per BSD release they generally blob the binaries that are compatible for
that release together.

No, pkgsrc is one for everyone, unless someone maintains his own branch.
As far as I know, only DragonFly and SmartOS do, though nothing serious
stops them from using original distribution. Thus NetBSD 6 and FreeBSD 9 use
the same version of GNOME, provided that they use supported pkgsrc branch.

DragonFly has a git mirror mirror of the pkgsrc cvs repository, but its contents are identical to what is in cvs.  I would not classify this as "maintaining its own branch".  We use the same distribution as NetBSD.

Just clarifying this statement to avoid misinformation.