I think you mis-understood Duncan's suggestion. What he is saying (as I
read it), is that you use svn branchaes to distinguish between these two
cases, like this:
-- Create a main branch (folder) that contains all the documents,
current and archive. A checkout from this branch will clearly fetch
*all* the documents, and so this folder is, in effect, a "full view" on
the document set.
-- Now, create a second "current" branch, and use the svn copy command
to branch the set of files you need from the main branch into this
current branch. A checkout from this branch will now only fetch the
"current" documents, and svn sill not complain about missing files etc etc.
-- Edit the current files in the current branch. After a commit, you can
merge the changes back into the main branch, which will make them
available in the *all* branch again.
You can also use the same technique to edit/merge changes to the
historical documents. In effect, you are using the branches as selected
subsets of the full tree.
--Tim
Michael Eager wrote:
> Gale, David wrote:
>> Michael Eager wrote:
>>
>>> Duncan Murdoch wrote:
>>>
>>>> On 5/19/2006 1:20 PM, Michael Eager wrote:
>>>>
>>>>
>>>>> I've just installed Subversion and I'm new using it.
>>>>> I want to use Subversion a little bit differently from
>>>>> the usual source code management application and I'd like a little
>>>>> advice.
>>>>> I want to create a document archive in Subversion.
>>>>> The archive will contain both current and historical
>>>>> documents. I want the working directory to contain
>>>>> only a subset of the files in the archive. I don't
>>>>> want Subversion to complain about the files which are
>>>>> missing from the working directory.
>>>>>
>>>>> Subversion (as far as I can tell) only allows me to
>>>>> checkout a full directory. Is there any way to check
>>>>> out specific files from an archive?
>>>>>
>>>>> Another alternative is to check out an entire directory
>>>>> and then delete the unwanted files from the working
>>>>> directory. Is there any way to tell Subversion to not
>>>>> complain about missing files, for example, in a "svn
>>>>> status" command? (I've thought about adding a command line option
>>>>> to do just this.)
>>>>> I've also thought about tagging old files with a
>>>>> property like "svn:archive". Is there any way to
>>>>> have Subversion only checkout certain files, such as
>>>>> ones which do not have this property.
>>>>>
>>>>> One idea which I considered and which does not work
>>>>> is to import the historical documents into the archive
>>>>> and then delete them. They are in the archive and
>>>>> can be recovered, but this makes them invisible when
>>>>> looking at the head of the revision tree, for example, when using
>>>>> ViewVC.
>>>>> Any ideas or suggestions?
>>>>
>>>>
>>>> I'd create two directories, "current" and "deleted". Check out
>>>> current, and when you don't want a document there any more, mv it to
>>>> deleted.
>>>> You may want multiple subdirectories in deleted, if you want to
>>>> re-use the same names for unrelated files, e.g. deleted/2005,
>>>> deleted/2006, etc.
>>>
>>> Yes, I thought about this, but it really doesn't address the problem.
>>>
>>> The historical documents are not "deleted", they are just inactive.
>>> When I need to update one of the historical documents, I want to be
>>> able to check it out of the archive and work on it in the correct
>>> place in the document tree. I don't want to have to check it out of a
>>> separate directory tree and move it to the real directory location.
>>>
>>> I want a single archive, not two.
>>>
>>> Thanks for the suggestion.
>>
>>
>> In that caase, it doesn't sound like subversion will give you what
>> you're looking for. Subversion requires you to check out an entire
>> directory, and if you delete a checked-out file, it'll reappear the next
>> time you do an update. If you want to use subversion, Duncan's solution
>> is probably the closest option you'll find; if that's not satisfactory,
>> I think you're going to have to do some poking around to find a
>> different version control system that allows for single-file checkouts
>> (I don't remember whether CVS allows this or not).
>
> I don't anticipate doing updates from the repository. This isn't source
> code management.
>
> Duncan's suggestion to create two different trees and manage them
> manually
> doesn't do what I want: maintain one archive where all documents reside,
> while only certain documents are present in the working directory.
>
> Managing two archives, one for current and one for historical, is
> error prone. Changes in the current directory, such as creating a
> new sub-directory or renaming files, would need to be done twice.
>
> As I said, possibly adding an option to SVN to simply not complain
> about deleted files might do what I want.
>
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Received on Sat May 20 03:14:58 2006