Skip site navigation (1)Skip section navigation (2)
Date:      Mon, 11 Feb 2002 07:26:15 -0500
From:      Will Andrews <will@csociety.org>
To:        Cy Schubert - CITS Open Systems Group <Cy.Schubert@uumail.gov.bc.ca>
Cc:        "Jacques A. Vidrine" <nectar@FreeBSD.org>, Cy Schubert <cy@FreeBSD.org>, cvs-committers@FreeBSD.org, cvs-all@FreeBSD.org
Subject:   Re: cvs commit: ports/security/krb5-beta [...]
Message-ID:  <20020211122615.GU82640@squall.waterspout.com>
In-Reply-To: <200202110319.g1B3JPu09732@cwsys.cwsent.com>
References:  <20020211015635.GB65324@madman.nectar.cc> <200202110319.g1B3JPu09732@cwsys.cwsent.com>

next in thread | previous in thread | raw e-mail | index | archive | help
On Sun, Feb 10, 2002 at 07:18:53PM -0800, Cy Schubert - CITS Open Systems Group wrote:
> In message <20020211015635.GB65324@madman.nectar.cc>, "Jacques A. Vidrine" writes:

I don't seem to remember getting this email, but...

> > The krb5-beta port has no history [1].  This is a scratch port for
> > people who want to beta test the next version of MIT Kerberos before
> > it is released.  When it is released, ports/security/krb5 will be
> > updated as appropriate and this port will be removed again.

In any case, intentionally putting a port in CVS for only a short
period is a waste either way since one could just as easily
request testers via the mailing list and this would work just
as well.

> > By contrast, a port called `krb5-devel' would be something different
> > (such as a development branch from CVS) and _would_ require a
> > repocopy.  Maybe this is what you have in mind.
> 
> I do have a "krb5-devel" port in mind, based on the daily krb5-current 
> snapshots.

Yes, that will certainly require one.

-- 
wca

To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe cvs-all" in the body of the message




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