Skip site navigation (1)Skip section navigation (2)
Date:      Sun, 9 Sep 2012 10:05:15 -0700 (PDT)
From:      Jeffrey Bouquet <jeffreybouquet@yahoo.com>
To:        Beat Gaetzi <beat@freebsd.org>, Lars Eighner <portsuser@larseighner.com>
Cc:        freebsd-ports@freebsd.org
Subject:   Re: [HEADS-UP] Announcing the end of port CVS
Message-ID:  <1347210315.97171.YahooMailClassic@web111315.mail.gq1.yahoo.com>
In-Reply-To: <alpine.BSF.2.00.1209070958550.1692@abbf.ynefrvtuareubzr.pbz>

next in thread | previous in thread | raw e-mail | index | archive | help


--- On Fri, 9/7/12, Lars Eighner <portsuser@larseighner.com> wrote:

> From: Lars Eighner <portsuser@larseighner.com>
> Subject: Re: [HEADS-UP] Announcing the end of port CVS
> To: "Beat Gaetzi" <beat@freebsd.org>
> Cc: freebsd-ports@freebsd.org
> Date: Friday, September 7, 2012, 8:00 AM
> On Fri, 7 Sep 2012, Beat Gaetzi
> wrote:
> 
> > The development of FreeBSD ports is done in Subversion
> nowadays.
> > For the sake of compatibility a Subversion to CVS
> exporter is
> > in place which has some limitations. For CVSup
> mirroring cvsup
> > based on Ezm3 is used which breaks regularly especially
> on amd64
> > and with Clang and becomes more and more
> unmaintainable.

The svn-book:
...you can edit files at will, but you must tell Subversion about
everything else that you do...

  Empirically, to a newbie, this appears quite confusing.  Are the
files in, say, /usr/ports/devel/boost-libs  "owned" in some manner by
svn? The extra files I've placed there (automatically generated
copies of work/.PList_flattened..)(etc) are ignored/accidentally erased? Lock files are no longer supposed to be placed in the
directory by scripts? 
...
  I had intended to simply restore an older copy of /usr/ports over
the new one, and have the two combined, as it were, but it appears
many unwanted effects (... only certain svn commands from now on?
Procedure to only .svn one of the port categories as can be done
with csup? Which svn commands transfer files from where to where 
etc.?) 
  Perhaps it would be better if I practice on the new ports tree
before restoring over it,  re-restore after practice, etc... 
Or even better, print out the online documentation, print out the
forum svn examples, and spend several weeks practicing for
csup equivalents and procedures... (That is what I am maybe 
wondering.  Has anyone done the same and written it all up in
a more detailed scenario? Which svn command subsets put files
not deeper in .svn at risk? Is there only one .svn or multiple 
ones? Which svn commands should be run just once, and which
routinely? Which to update just one parts of the ports tree?
...
Even commands to copy the ports tree elsewhere with a lesser 
volume of files (no .svn... )  
(Subversion appears more of an administrative tool rather than
an end-user tool; requiring more complex configuration maybe, 
though maybe not if just for the ports tree.  Possible 
configuration files to examine/copy persons may have already
working for user/ports?)

  I'd rather use portsnap only on an older laptop... otherwise
I would defer to it instead (for now anyway, since there is
still time left...)

  BTW in replies to a question on the freebsd-questions list, I
surmise there are many server farm administrators who are
comfortable with csup/cvsup and not yet familiar with svn, and
may also be thrown a learning curve with this change.

  Apologies for asking here, but trying to save many hours (or
even minutes) of
web searching, trial and error, etc...


J. Bouquet





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