Linked by Thom Holwerda on Thu 22nd Nov 2007 16:59 UTC, submitted by Oliver
BSD and Darwin derivatives "DesktopBSD 1.6RC3 for AMD64 is now available for download via BitTorrent and from our mirror sites. It includes several improvements made since the release of 1.6RC3 for i386, including: better performance by disabling SMP on single core/processor computers, fixed installation on disks with special partition names, inclusion of the FreeBSD ports collection on the DVD, and more."
Thread beginning with comment 286058
To view parent comment, click here.
To read all comments associated with this story, please click here.
RE: Good news
by Aaron1 on Fri 23rd Nov 2007 03:00 UTC in reply to "Good news"
Aaron1
Member since:
2006-01-19

I maybe wrong here but I think PC-BSD still includes the ports system if you want to use it.

Reply Parent Score: 2

RE[2]: Good news
by Doc Pain on Fri 23rd Nov 2007 03:11 in reply to "RE: Good news"
Doc Pain Member since:
2006-10-08

"I maybe wrong here but I think PC-BSD still includes the ports system if you want to use it."

In fact, PC-BSD, as well as DesktopBSD, contain both facilities for using precompiled packages and the ports collection. Please pay attention that using them with PC-BSD is possible, but not recommended unless you're exactly knowing what you do, because it may interfere with the PBI system.

So, on a PC-BSD and a DesktopBSD system, you can

# pkg_add -r xmms

to install from a precompiled package, wich will install the dependencies if required, or

# cd /usr/ports/multimedia/mplayer
# make install

to compile and install from a ports entry.

Compiling things from the ports is needed only if you want to run bleeding edge software or if you are required to set configuration flags at compile time (e. g. codes to use by mplayer, or recompile X to make a tree button mouse work properly). In most cases, pkg_add is what you want.

You can use the portupgrade frontends (portinstall, portupgrade, pkgdb) to make extended use of the ports system and have a both ports and packages aware database maintained automatically (pkgdb -aF).

Reply Parent Score: 6

RE[2]: Good news
by tankist on Fri 23rd Nov 2007 18:25 in reply to "RE: Good news"
tankist Member since:
2007-01-19

If you browse the PC BSD forums you'll see numerous complains about problems after installing software using port/packages. It looks that PBIs are not that compatible with the standard FreeBSD way of installing software.

Reply Parent Score: 1

RE[3]: Good news
by Doc Pain on Sat 24th Nov 2007 08:43 in reply to "RE[2]: Good news"
Doc Pain Member since:
2006-10-08

"It looks that PBIs are not that compatible with the standard FreeBSD way of installing software."

No, it's the other way round: If you use PBIs only in PC-BSD, you shouldn't run into problems. If you start using ports / packages with PC-BSD, it might (!) cause problems with certain applications, but if you're lucky, you're using the ones that work without interferences.

But finally, your statement is correct. PBI introduced new paths that are not compatible with FreeBSDs standard locations for software installation (read "man hier" for more info).

Reply Parent Score: 2

RE[4]: Good news
by antik on Sat 24th Nov 2007 10:30 in reply to "RE[2]: Good news"
antik Member since:
2006-05-19

"It looks that PBIs are not that compatible with the standard FreeBSD way of installing software."

No, it's the other way round: If you use PBIs only in PC-BSD, you shouldn't run into problems. If you start using ports / packages with PC-BSD, it might (!) cause problems with certain applications, but if you're lucky, you're using the ones that work without interferences.

But finally, your statement is correct. PBI introduced new paths that are not compatible with FreeBSDs standard locations for software installation (read "man hier" for more info).


1) All PBIs are installed into /usr/local/Programs (compatible with hier btw).
2) About "broken" ports- due to license issues we can't provide restricted audio/video codecs like win32codec, so we are forced to remove it from PC-BSD- this causes your so called "broken ports". If you know what are your doing then you can fix this issue in no time.

# pkgdb -F

and stop whining...

Reply Parent Score: 3