I have to say that I'm a big fan of FreeBSD as well. I have linux
machines, windows machines, MacOSX machines, and FreeBSD machines, and
out of all of them, I've had the fewest problems with the FreeBSD
machines. As Graham points out, linux machines have a habbit of
updating everything under the sun just for a simple upgrade, and that
can get expensive timewise and downloading time invested. When I need
to update something in BSD, I just hop over to the packages directory,
and update that speecific package, and all continues to work as it has.
FPC isn't always the latest, but since I compiled my own copy, that's
not really an issue for me.
I too prefer to install from source, since that way, if my particular
setup encounters a problem (as oes happen from time to time) it's
relatively easy to solve with some judicial editing of source, then
recompiling. Generally, it's quick and simple, and painless. I Like
linux too, but for different reasons. I used to use linux for my
hosting, but if I ever did the selling hosting services I hosted myself
thing again, I'd definitely use FreeBSD instead of linux for the servers.
On 3/13/2017 5:45 AM, Graeme Geldenhuys wrote:
On 2017-03-13 02:50, [email protected] wrote:
What do you mean by binary package systems:
https://www.freebsd.org/doc/handbook/pkgng-intro.html
Yes, that. And in Linux terms, it would be *.deb, *.rpm etc files.
To give you an example of "binary package dependency hell" - which I
hate. Say I prefer to run Firebird RDBMS v2.1.x for some specific
reason, but I also like to use the utility FlameRobin to connect and
manage my Firebird databases. Now a new version of FlameRobin comes out,
and it has a feature I would like to use.
With binary packages, they will link FlameRobin to the latest Firebird
v2.5 or now even v3.0 client libraries, which in turn might link to the
Firebird v2.5 or v3.0 Firebird Database Server package.
So if I wanted to upgrade FlameRobin, it would upgrade the database
client libraries and might upgrade the data server. This has actually
happened to me under Ubuntu Linux before.
That is definitely not something I would have liked or wanted. So with
FreeBSD's ports system, everything is more modular and configurable, and
even though everything is also compiled from source code, the FreeBSD
team has made it super simple and uncomplicated (I know nothing about
C/C++ development and I have limit knowledge about Makefiles). The
FreeBSD ports system hides all that from you with simple commands no
matter the ports package.
$ make config // to configure dependencies and features.
$ make install clean // compile, install and clean-up afterwards
$ make deinstall // uninstall something - without
// recursively uninstalling dependencies or
// dependants.
Also, the base OS installs things in /etc/ and /usr/bin and /usr/sbin.
User installed programs and libraries (both not part of the base OS)
install things into /usr/local/etc/ and /usr/local/bin/
Nice and clear separation, and things NEVER get mixed up.
Regards,
Graeme
---
This email has been checked for viruses by Avast antivirus software.
https://www.avast.com/antivirus
_______________________________________________
fpc-other maillist - [email protected]
http://lists.freepascal.org/cgi-bin/mailman/listinfo/fpc-other
