Skip site navigation (1)Skip section navigation (2)
Date:      Sun, 26 Sep 2010 13:25:30 +0100
From:      Matthew Seaman <m.seaman@infracaninophile.co.uk>
To:        Michel Talon <talon@lpthe.jussieu.fr>
Cc:        questions@freebsd.org
Subject:   Re: Free BSD 8.1
Message-ID:  <4C9F3BBA.2060809@infracaninophile.co.uk>
In-Reply-To: <20100926123019.GA41450@lpthe.jussieu.fr>
References:  <20100926123019.GA41450@lpthe.jussieu.fr>

next in thread | previous in thread | raw e-mail | index | archive | help
This is an OpenPGP/MIME signed message (RFC 2440 and 3156)
--------------enigAF1F11DCE34514FA98363B17
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: quoted-printable

On 26/09/2010 13:30:19, Michel Talon wrote:
> Matthew Seaman said
>=20
>> Be aware that installing the ports tree from the DVD images is not the=

>> ideal way to do it.  If you have the connectivity on your newly
>> installed system, it is better to use either csup(1) or portsnap(1) to=

>> grab an up-to-date copy of the ports directly from the net.
>=20
> I disagree with that. You are supposing that newer is better, which is
> far from proven (in fact blatantly false in many cases). Another option=

> is to install the ports tree from the  DVD,and install corresponding
> precompiled packages from the DVD or otherwise the web, and
> *not* updating the ports tree. There is a lot to be said for this
> option, and many users will be happier doing that, at least people who
> want to use their machine and not spend their time upgrading, compiling=

> and fighting bugs.
>=20

No.  I made no comment on the relative advantages and disadvantages of
various updating strategies.  Please do not put words into my mouth.
Given that the OP asked about the ports I think it fairly safe to assume
that his intention was to use them.

And, yes, being up-to-date with the ports tree generally *does* give you
better results than not.  Ports are a moving target, dependent entirely
on upstream changes.  Expecting that a snapshot taken months or weeks
ago will work just as well as one updated in the last hour is plain
daft.  Even without any functional changes to the ported software,
projects still move to different hosting, URLs change as archive sites
are internally reorganised, ftp servers come and go, dist files get
re-rolled with new checksums.

Aside from those neutral changes, ported software generally does improve
over time.  Updates that fix problems are way more common that updates
that introduce them.  Despite a few high-profile occasions when things
have gone horribly wrong -- not just with the ports, but with any OSS
project --- this is overwhelmingly the case.  The quality control in the
majority of large OSS projects is very good nowadays -- probably better
than their closed source equivalents.  End users can quite reasonably
expect not to have to spend their time "fighting bugs."
Newer generally /is/ better.

Besides that, the assumption you are making, that change is undesirable,
is just plain wrong.  People will always want new stuff.  It may not be
wise for them to get it, but that's another story.

	Cheers,

	Matthew

--=20
Dr Matthew J Seaman MA, D.Phil.                   7 Priory Courtyard
                                                  Flat 3
PGP: http://www.infracaninophile.co.uk/pgpkey     Ramsgate
JID: matthew@infracaninophile.co.uk               Kent, CT11 9PW


--------------enigAF1F11DCE34514FA98363B17
Content-Type: application/pgp-signature; name="signature.asc"
Content-Description: OpenPGP digital signature
Content-Disposition: attachment; filename="signature.asc"

-----BEGIN PGP SIGNATURE-----
Version: GnuPG/MacGPG2 v2.0.14 (Darwin)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/

iEYEARECAAYFAkyfO8IACgkQ8Mjk52CukIwd9ACfeN0+6L9dtHcUS8gcgEPyaLjr
WIEAn3xdFITmhueBmMTY72U0yjL2aEhP
=5RLp
-----END PGP SIGNATURE-----

--------------enigAF1F11DCE34514FA98363B17--



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