Skip site navigation (1)Skip section navigation (2)
Date:      Tue, 19 Apr 2005 20:37:43 -0600
From:      Brett Glass <brett@lariat.org>
To:        questions@freebsd.org
Cc:        Kris Kennaway <kris@obsecurity.org>
Subject:   Re: Can't build ports on older FreeBSD machine
Message-ID:  <6.2.1.2.2.20050419203347.05bed918@localhost>
In-Reply-To: <20050419043330.GA92736@xor.obsecurity.org>
References:  <200504180758.BAA10753@lariat.org> <20050419031952.GA90643@xor.obsecurity.org> <6.2.1.2.2.20050418213725.0591beb0@localhost> <20050419041638.GA56099@xor.obsecurity.org> <6.2.1.2.2.20050418222126.04ea4660@localhost> <20050419043330.GA92736@xor.obsecurity.org>

next in thread | previous in thread | raw e-mail | index | archive | help
At 10:33 PM 4/18/2005, Kris Kennaway wrote:

>OK, but I don't care about your HO on this matter.

You may not, but users of FreeBSD do. At the very least,
ports should be tagged as to the versions of the OS
with which they will work, and it should be possible
to retrieve the most recent version of the port that
works with the version of the OS you are running.
Having users update in the standard (and prescribed)
way and finding out that a major function (the entire
ports system) is no longer working is certainly not
something one would expect from professionally crafted
software.

Note that under Linux, the maintainers of distributions
do exactly this. However, FreeBSD is essentially its own
"distro," so the job of doing this falls to the FreeBSD
developers and the maintainers of the ports. If it is
not done, FreeBSD users will enjoy an inferior experience
to the one they get with Linux or even Windows.

--Brett Glass



Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?6.2.1.2.2.20050419203347.05bed918>