>>>>> "Chris" == Chris Parker <chris@playswithfire.com> writes:
Chris> On Mon, Nov 17, 2003 at 01:00:19AM +0100, Lele Gaifax
Chris> wrote:
>> Yes, in ancient NeXT days, there was something like that (was
>> it CVSPalette?), an IB extension that, using pre/post write
>> hooks in IB copied .svn/ from the .nib~ folder to the new
>> .nib/... I remember also a "dirty" hack on CVS modules
>> functionality, called "wrappers", that in my opinion would be
>> the right way of dealing with the problem.
Chris> No.
No what?
Chris> I can't repeat that enough times. Fitz and a few others are
Chris> probably wondering just -when- I'm going to read this email
Chris> and refer you to:
Chris> http://subversion.tigris.org/issues/show_bug.cgi?id=707
Chris> Which would be the Right Way to handle this kind of
Chris> situation, and get everyone completely away from the
Chris> wrapper idea.
I miss your point: issue 707 talks about an "opaque" collection, it
does not clarify in what way this would be different from the wrapper
concept. You are apparently against "tar", but I do not see an evident
reason for which the "storage" of a particular subtree of your repos
(be it a .nib folder, or a deeper hierachy that, for whatever reasons,
you want keep zipped+signed in the repository) couldn't be decided by
the user/developer/admin. I do surely know, by now, that this isn't
exacly svn' field, but I still consider that some support from it would
be welcome if not needed.
Chris> People who helped implement the wrapper idea
Chris> think it's a bad idea. The synchronization issue alone of
Chris> implementing the wrapper gives most CVS admins fits, and
Chris> for good reason.
Chris, I do *know*, having used that functionality *while* "people"
(bbum, primarily) was implementing it :). Sooner or later I will have
to convert my oldest CVS repos, that used that hack, while the
NeXTstation keeps booting... :-|
AFAICT, it was the /implementation/ of the thing that was "dirty", not
the concept.
Chris> Note that (unfortunately) IB in Panther has the ability to
Chris> listen for a default for this kind of thing:
Chris> 'defaults write com.apple.InterfaceBuilder
Chris> VersionControlDirectory "(CVS, .svn)"'
Chris> will allow you to preserve your version control admin
Chris> directories of choice. You'll still have to manually 'svn
Chris> add' or 'svn remove' if you put things -in- nibs but IB can
Chris> at least preserve the directories, limiting the requirement
Chris> for wrappers use.
Yes, but from a different PoV, this somewhat breaks the admirable
concept of "app-folders", of which usually the user shouldn't even
need to know the internal layout. As said, having used it, the
potential of going out-of-sync is very high ("did I add *every* file
in the .nib/ folder?" and the like). Consider the .rtfd/ folders (are
those still there?): I can immagine that, once I import the first
version of the document, I'd prefer that in some way svn could
understand what I really want: whatever I drop in my doc (an image, me
saying "hello".snd...), is stored somewhere (usually with a serial id
as name, not the original) within the .rtfd/ sub-hierarchy and should
be *automatically* considered a "part of the document" that was
modified. Can you show me a case where you do not want to "svn add"
that file, *before* committing the folder? Again, I know, many think
this is a frontend related problem...
ciao, lele.
--
nickname: Lele Gaifax | Quando vivrò di quello che ho pensato ieri
real: Emanuele Gaifas | comincerò ad aver paura di chi mi copia.
email: lele@seldati.it | -- Fortunato Depero, 1929.
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Received on Mon Nov 17 02:28:07 2003