--+mr2ctTDD1GjnQwB
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
Content-Transfer-Encoding: quoted-printable

hi,

On Fri, May 07, 2004 at 08:00:04AM -0700, Jeremy C. Reed wrote:
> On 7 May 2004, Nicola Bolla wrote:
>=20
> > experience: in particular, I was disappointed to discover that some
> > of the compiling errors I had, magically disappeared as soon as I
> > decided to restart from zero the whole process, from a clean
> > situation. I think that is due to the fact that while I am building
> > my workstation environment, package after package, day after day,
> > the pkgsrc tree keep on changing, hour after hour, under the effect
> > of the commit activity of the maintainers. So, it happens that while
> > I am building a new package, maybe that some packages (already
> > installed) on which the new package depends are out of sync,
> > compared with the current release/version in pkgsrc. I don't want
> > that this situation could cause errors in the building of new
> > packages, otherwise I louse time and I risk (and this is bad) to
> > make louse the time of the kind people of the list who are trying to
> > help me.
> >
> > Which is, in your experience, the best strategy to manage this
> > problem?
>=20
> One idea is to use the "stable" version of pkgsrc. In CVS it is tagged
> as "pkgsrc-2003Q4". It only has changes for security fixes and a few
> infrastructure or build problems.

the pkgsrc-2003Q4 branch is not supported anymore.  the latest stable
branch is pkgsrc-2004Q1.


regards,

--=20
-- Lubomir Sedlacik <salo@{NetBSD,Xtrmntr,silcnet}.org>   --

--+mr2ctTDD1GjnQwB
Content-Type: application/pgp-signature
Content-Disposition: inline

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.4 (NetBSD)

iD8DBQFAm6eDiwjDDlS8cmMRAqZyAJ90gZQtKFFMp1U6KBv79FJoJHvgkgCfc/Wk
nr65hQ6ECtt/bENzh2aFMY8=
=uza7
-----END PGP SIGNATURE-----

--+mr2ctTDD1GjnQwB--