[kris@FreeBSD.org: cvs commit: ports/net/cvsupit Makefile]

[Jordan K Hubbard]

I'm not sure I agree.  It seems far preferable to "ask around" for 
someone to do this the right way instead.

- Jordan

On Tuesday, May 6, 2003, at 01:52 AM, Kris Kennaway wrote:

> On Tue, May 06, 2003 at 12:59:40AM -0700, Jordan K Hubbard wrote:
>> Sorry, I simply haven't fixed it yet since I'm now having a hard time
>> deciding, upon further reflection, whether I shouldn't just kill that
>> stupid port.  cvsupit started life as a crufty quick hack meant to 
>> fill
>> a short-term purpose (get newbies introduced to cvsup at the time) and
>> doesn't serve the longer-term purpose of making cvsup easy to use
>> throughout FreeBSD's lifetime.
>>
>> To do that, if it's even desired, will require release engineering
>> assistance to spit out customized cvsupfiles which match whichever 
>> tags
>> are currently in vogue, present dynamic menus of available choices,
>> etc.  In short, if people really want "cvsupit-like" functionality for
>> the long-term then they're just going to have to embed it into the
>> "process chain" for release engineering somehow and not just rely on
>> some crufty port staying in sync.  The "keep the crufty port in sync"
>> approach has worked for awhil, but it just isn't practical, IMO,  to
>> continue doing so any longer.  That's unless someone else really has a
>> strong lust to step forward and take the cvsupit port over for further
>> life-support efforts.
>
> I believe it's still widely used, so if we need to find a new
> maintainer then we should ask around.
>
> Kris
> <mime-attachment>
--
Jordan K. Hubbard
Engineering Manager, BSD technology group
Apple Computer