Re: Mac OS X "packages" Best Practices?

[Markus <yo...@hispeed.ch>]

>> As far as svn stands, I think we're all at the position of "it would
>> be really nice if svn could treat some directories as opaque/atomic
>> but that isn't going to happen any time soon."
> 
> In short, what it comes down to, is that this feature is fairly 
> difficult to implement within the boundaries of the current working 
> copy design.  In order for it to get implemented, a well thought out 
> design on how to implement it is going to be needed.  The good news is 
> that in the last couple of releases developers have been optimizing the 
> working copy design and code, which means there are more developers who 
> have been working in that area of the code and are feeling more 
> comfortable with it.  So if a design were to emerge, there are 
> developers that should be able to comment on the proposal and help 
> refine it.
> Mark

Shouldn't it be fairly easy for an OS X subversion client to zip all 
bundles and tag the bundles itself to be ignored before it applied any 
'real' svn commands and in reverse whenever receiving any zip files, 
unzip them, check whether they are bundles (and if not delete the 
unzipped stuff).

I have only a few days ago started working with svn, so I probably have 
no real idea of what is easy or feasible but if the lack of a concept 
to solve this problem is the main issue, maybe this might be a lead.

This approach assumes that people who care about bundles also run svn 
clients only on OS X since only OS X client would implement this 
approach. Moreover, adding functionality to the subversion client for 
only one platform would go against the whole idea of platform 
independent code which would be probably not be very appreciated by the 
subversion developers.

Therefore, I would propose to implement this idea only in OS X GUI 
clients, which already are in several cases OS X-only. It should be 
seen as a feature of the OS X GUI client and not of subversion itself. 
It is only an interim solution until the opaque/atomic tag would be in 
subversion itself.

Markus



---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org

Re: Mac OS X "packages" Best Practices?

[Markus <yo...@hispeed.ch>]

> I think, if I recall correctly, that a number of people already have 
> script s that handle this.
> 
> In any event, see
> 
>     <http://subversion.tigris.org/issues/show_bug.cgi?id=707>
>     for a discussion of this problem.
> 
> -Mike

I have read through the whole long thread in this newsgroup (the one 
that started in March this year) and I have also read through the 
comments in the link above but I could not find a reference to a script 
which does this (I am sure somebody must have created one). If somebody 
would be willing to share such a script, I think this could be useful 
to a number of people.

Markus



---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org

Re: Mac OS X "packages" Best Practices?

[Mike Conley <no...@crystalmaker.com>]

On 24.09.2006, at 23.53 (UTC+0200), Markus scribbled thusly:

>Shouldn't it be fairly easy for an OS X subversion client to zip all 
>bundles and tag the bundles itself to be ignored before it applied any 
>'real' svn commands and in reverse whenever receiving any zip files, 
>unzip them, check whether they are bundles (and if not delete the 
>unzipped stuff).

I think a lot of people probably already do this. For a variety of reasons, all of which have been enumerated in the past, this is not an optimal solution.

>This approach assumes that people who care about bundles also run svn 
>clients only on OS X since only OS X client would implement this 
>approach.

That's an invalid assumption, on two counts: it assumes that only Mac OS X users are interested in opaque directories (or bundles), and it assumes that one would only ever be interested in checking Mac OS X code in or out onto a Mac platform. I, for example, do all of my Windows code editing on my Mac; I don't think it's a stretch to imagine that there might be people out there who occasionally (or regularly) need to edit Mac code from a Windows (or Linux, or whatever) box.

And opaque directories are useful for other platforms besides the Mac.

>Moreover, adding functionality to the subversion client for 
>only one platform would go against the whole idea of platform 
>independent code which would be probably not be very appreciated by the 
>subversion developers.

One could argue that SVN has broken platform independence because one of the primary features of a not-insignificant platform which it supposedly supports is not properly (and transparently) supported.

>Therefore, I would propose to implement this idea only in OS X GUI 
>clients, which already are in several cases OS X-only.

I think, if I recall correctly, that a number of people already have scripts that handle this.

In any event, see

    <http://subversion.tigris.org/issues/show_bug.cgi?id=707>
    
for a discussion of this problem.

-Mike

---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org