rcs is gone?

John-Mark Gurney jmg at funkthat.com
Tue Oct 8 02:24:33 UTC 2013


Glen Barber wrote this message on Mon, Oct 07, 2013 at 20:59 -0400:
> On Mon, Oct 07, 2013 at 05:54:23PM -0700, John-Mark Gurney wrote:
> > > No, not really.
> > > 
> > >     # mkdir local
> > >     # svnadmin create ./local
> > >     # svn import /etc file:///$PWD/local
> > 
> > besides the s/svn/svnlite/ you forgot...  It doesn't work...  Sure it
> 
> WITH_SVN in src.conf will install svnlite as svn.
> 
> > imports all of my /etc, but doesn't let me commit my changes to rc.conf:
> > # svnlite commit rc.conf
> > svn: E155007: '/etc/rc.conf' is not a working copy
> 
> Sure it does.
> 
> gjb at nucleus:~/svn % mkdir local
> gjb at nucleus:~/svn % svnadmin create ./local
> gjb at nucleus:~/svn % cp -rp /usr/local/etc/rc.d fakelocaletc
> gjb at nucleus:~/svn % svn import ./fakelocaletc file:///$PWD/local -m "Initial import."
> gjb at nucleus:~/svn % svn co --force file:///$PWD/local fakelocaletc

This is the step you forgot to include previously...  So, it's still
a multistep process before you can revision control the files and clearly
not simple since we already have two different ways of doing it...

I wouldn't have even thought about the permission issue that someone
else brought up...

> Checked out revision 1.
> gjb at nucleus:~/svn % svn stat !$
> svn stat fakelocaletc
> gjb at nucleus:~/svn % svn info fakelocaletc
> Path: fakelocaletc
> Working Copy Root Path: /usr/home/gjb/svn/fakelocaletc
> URL: file:///home/gjb/svn/local
> Relative URL: ^/
> 
> > Plus, I was quite reasured that svn isn't smart enough to realize that
> > a path might be a file: url relative to the current working directory...
> 
> I don't know what you mean by this.

svn didn't bother trying to figure out if the relative path (or even
absolute path) has a valid repo.. it just decided, nope, not a URL,
I'll quit now, even though it could have been smart...

-- 
  John-Mark Gurney				Voice: +1 415 225 5579

     "All that I will do, has been done, All that I have, has not."


More information about the freebsd-current mailing list