Subject: Re: CVS commit: pkgsrc/devel/gdb6
To: None <tech-pkg@NetBSD.org>
From: John R. Shannon <firstname.lastname@example.org>
Date: 06/01/2004 14:10:28
=2D----BEGIN PGP SIGNED MESSAGE-----
On Tuesday 01 June 2004 01:39 pm, Jeremy C. Reed wrote:
> On Tue, 1 Jun 2004, John R. Shannon wrote:
> > Log Message:
> > gdb6 The GNU Project Debugger revision 6.1
> > This is a new package.
> Should we keep old gdb-5.3 around?
> Often, when we have two versions, we put the old version with a package
> name that also has a version number. For example:
> devel/gdb would be your new gdb-6.1
> devel/gdb5 would be old gdb-5.3nb2
> One reason is if someone wants to keep using the latest and greatest they
> don't have to learn about your new gdb6 package, but can just update gdb.
I see your point. Running lintpkgsrc -i will miss the newer package.
> Also, can someone explain to me the pros and cons of using "cvs import"
> when importing new packages?
"NOTE: "cvs import" is preferred to "cvs add" because the former gets=20
everything with a single command, and provides a consistent tag."=20
John R. Shannon
=2D----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.4 (NetBSD)
=2D----END PGP SIGNATURE-----