| Re: Source code management with IDL Workbench [message #57551 is a reply to message #57550] |
Thu, 13 December 2007 15:51   |
Michael Galloy
Messages: 1114
Registered: April 2006
|
Senior Member |
|
|
On Dec 13, 2:23 pm, David Fanning <n...@dfanning.com> wrote:
> Mike Galloy writes:
>> In my experience, every way of adding files to a repository requires
>> checking out the repository first. The Subversion book says about "svn
>> add":
>
>> "Add files, directories, or symbolic links to your working copy and
>> schedule them for addition to the repository. They will be uploaded
>> and added to the repository on your next commit. If you add something
>> and change your mind before committing, you can unschedule the
>> addition using svn revert."
>
>> So I think that means you have to have a working copy first.
>
>> But, why would you do that? Don't you need to have a local copy of
>> everything working, test it, etc. AND then check in the file? I
>> suppose if you had a library of completely unrelated routines then
>> adding them directly would make sense.
>
> Alright, you are totally confusing me. :-)
>
> I have set up a Subversion repository. And I have IDL programs,
> sitting right here in a directory on my C drive that
> I want to add to the repository. How do I do that from
> within IDL?
Vince's technique about using "import" in the SVN Repository
Perspective is the right one to add stuff directly to the repo. But
note that you will still have to checkout the repo in order to have a
local working copy (i.e. the imported files are not under version
control).
I guess I just always start by checking out a directory from the repo
(even if it is just an empty directory) and gradually adding to it as
I verify that each addition still leaves everything working. Importing
stuff directly to the repo just seems a bit dangerous to me.
Mike
--
www.michaelgalloy.com
Tech-X Corporation
Software Developer II
|
|
|
|
comp.lang.idl-pvwave archive
Members
Search
Help
Login
Home
