Skip site navigation (1)Skip section navigation (2)
Date:      Mon, 16 Jan 1995 12:10:24 -0800 (PST)
From:      "Rodney W. Grimes" <rgrimes@gndrsh.aac.dev.com>
To:        paul@isl.cf.ac.uk (Paul Richards)
Cc:        pst@shockwave.com, ache@astral.msk.su, CVS-commiters@freefall.cdrom.com, cvs-CVSROOT@freefall.cdrom.com
Subject:   Re: cvs commit: CVSROOT modules
Message-ID:  <199501162010.MAA01384@gndrsh.aac.dev.com>
In-Reply-To: <199501161446.OAA02005@isl.cf.ac.uk> from "Paul Richards" at Jan 16, 95 02:46:23 pm

next in thread | previous in thread | raw e-mail | index | archive | help
> 
> In reply to Paul Traina who said
> > 
> > There was no way to load groff-1.09 on top of the groff-1.08+freebsd
> > because the person who originally did the groff port screwed with the
> > directory heirarchy,  so I just created a new groff port and am layering
> > changes necessary for compilation (plus all of your 8 bit clean changes et al).
> > 
> > Once everyone's happy with ngroff, we change the makefile to build it instead
> > of groff, then we wait n months and destroy groff and rename ngroff to groff.
> > 
> 
> Please, no-one do any more of this.
> 
> Those of use who sup the cvs tree get stuck with this forever since
> groff will always be in the cvs tree and if this carries on eventually
> even those of us with lots (I have 2 Gb) of disk are going to have
> to bail out.
> 
> I guess the only way to do this is to remove all the current files and then
> import into the same area of the tree. That's what I did when I ditched the
> old libforms and imported a completely new one although I admit that
> was a much simpler job. The principle's the same though.

The best solution I can see to this problem is to rename the current gnu
src tree to ognu, those supping can rename this locally before they sup
after the rename, create a new area gnu that is empty, start to import
and work in there.  Once it is all moved to the new gnu area we can simply
stop supping the old one.

This will create the anomoly that when you cvs co the old 2.0 release from
cvs on freefall you will end up with /usr/src/ognu.

The other alternative would be to create /usr/src/ngnu and live with that
name forever, once all the bits are imported and set up in there correctly
simply stop supping src/gnu.  (Same idea, only different names).

>   Paul Richards, FreeBSD core team member. 

-- 
Rod Grimes                                      rgrimes@gndrsh.aac.dev.com
Accurate Automation Company                   Custom computers for FreeBSD



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