Rant: are we falling apart or is it just a coincidence?

[teo]

PC-BSD is far from called a sitema, heavy. PC-BSD does not have 32-bit OS, it is better to build FreeBSD with desk.
The question is, while they are working on that project can not build a good system, this project is several years old.

 

[AzaShog]

The first three sentences on the front and top of their web site home page all exclaim it's a desktop operating system based on FreeBSD so I don't see how you can say it's not.

I said it was not a variant of FreeBSD, it's an entirely separate OS for all intents and purposes, with its own server variant even (TrueOS), and until recently its own packaging system... If it were just a variant of FreeBSD, it would be something you can install and run on FreeBSD base. And yes, I know you can "turn" FreeBSD into PC-BSD, that's not what I mean.

Because to extend your logic, I know of another desktop OS "based" on BSD... why not use that then.

 

[drhowarddrfine]

I said it was not a variant of FreeBSD, it's an entirely separate OS for all intents and purposes, with its own server variant even (TrueOS)

I think you're trying to make it something it's not. PC-BSD has the complete FreeBSD system built in and only surrounds that with some of its own packages and packaging system. The same is true of TrueOS.

This whole thread we're running now may be entertaining but I find it quite boring so I won't continue with it.

btw, I'm writing this from PC-BSD running in a VM on my current system with Chromium running Lumina though I had switched from KDE.

 

[jb_fvwm2]

It is not technically practical to use both package systems. What the new system really needs is automated testing. That said, I've had no problems using it with ports.

Permit a rephrasing of sorts of my post... what I learned since I posted it. Maybe some ports could be managed by pkg and a subset managed by a registration-into registration-out-of [by some new command] the files produced by the sum of pkg info -R port and pkg info -r port; one could thus install and record a port that otherwise could not be installed due to, say, a manpage name conflict one would not care about. In a more involved sense, those two pkg info commands could maybe serve as a registration alternative local.sqlite.but-txt or something. Unclear here but plausible maybe...

 

[wblock@]

The old package tools are dead. Please stop trying to reanimate them. We know how that story ends.

The new package tools are better. That is the place to focus efforts on improvement. Test. Submit PRs. But don't do it with one foot in the past.