Since I haven't had any response to this scenario, I assume people
aren't really doing things this way. That makes me wonder, then, how
other *are* handling hotfix packaging and delivery. Do you ship the
entire code base when only a few files have been changed? If not, how
do you maintain the directory structure for the few files that *have*
changed?
On 7/27/06, Rob Wilkerson <r.d.wilkerson@gmail.com> wrote:
> That's not quite what I'm after, so bear with me while I try to do a
> better job of explaining. What I'm really looking for is a way to
> facilitate packaging a hotfix that does *not* include the entire code
> base. What I'd like to be able to do is tag a set of changes, but
> only include the file structure that is relevant to the modified
> files. So:
>
> I have a directory structure in which there is a root directory and 5
> sub-directories like so:
>
> productroot/
> /sub1
> /file1
> /sub2
> /file2
> /sub3
> /file3
> /sub4
> /file4
> /sub5
> /file5
>
> I modify file3 and file5 and decided to put that out as a hotfix. I
> don't want to re-package the entire code base, but I want to maintain
> the structure that is relevant to those files. I'd like to create a
> tarball for the hotfix such that customers can place that tarball in
> their product root directory and simply unpack it and the old files
> will be replaced with the modified.
>
> I don't think my issue has as much to do with working within the
> repository as it does with extracting subsets *from* the repository.
> Does that make any more sense? Are others handling things
> differently? That's just the way my maintenance release process has
> worked - but it's always been a manual effort using VSS. I was hoping
> svn would help automate it a bit.
>
> Thanks for your help.
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Received on Fri Jul 28 13:51:24 2006