Question from a newbie...

[Flapflap <li...@sans-facon.net>]

Hi there,

I'm new to subversion so hello everyone.

I'm just installed and tested subversion from my local work network and 
all works fine.

Just a few question about some things I would like to make but haven't 
find in doc...

Would like that  :

1- when somebody make an update, the file is automatically llock.

2- when somebody commit is file it automatically will be unlock (i think 
it's all ready the case)

3- when commit is file, is local version file be marked as read-only (I 
got Windows (TSVN) and Mac Os X (SVNX) clients)

4- all my repository (I'll make one by project) get the same use / 
password list so I don't have to copy it every time I create a new 
repository

Is it possible ?
Can you give me some way to go for this ?

Thanks for any help.
Sorry for bad English...

-- 
Flapflap[at]sans-facon.net --
DevBlog : http://www.kilooctet.net


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

Re: Question from a newbie...

[Andy Levy <an...@gmail.com>]

On 11/25/05, Flapflap <li...@sans-facon.net> wrote:
> Hi there,
>
> I'm new to subversion so hello everyone.
>
> I'm just installed and tested subversion from my local work network and
> all works fine.
>
> Just a few question about some things I would like to make but haven't
> find in doc...
>
> Would like that  :
>
> 1- when somebody make an update, the file is automatically llock.
>
> 2- when somebody commit is file it automatically will be unlock (i think
> it's all ready the case)
>
> 3- when commit is file, is local version file be marked as read-only (I
> got Windows (TSVN) and Mac Os X (SVNX) clients)

It sounds like you want Subversion to work just like Visual
SourceSafe.  The two products are designed for very different
workflows/philosophies.

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

Re: Question from a newbie...

[Célio Cidral Junior <cc...@gmail.com>]

2005/11/25, Flapflap <li...@sans-facon.net>:
> Hi,
>
> First thanks for your reply.
>
> Ok so Subversion is maybe not the good tool for me. I mean we worked
> mostly on flash project so Flash Binary files can't have the "dif way"
> so i was thinking on use the "lock way".... Hope I'm clear...

You can lock your files by explicitly calling the lock command. The
update command can't do it for you. So, you and your team mates will
have to remember to explicitly lock the binary files before change
them.

> >You can create only one authz file and use it for several
> >repositories. That's what we use here in my company
> >
> >
> Is this only possible with apache (I use svnserve for now)

My apologies, I may have confused you. Authorization (per-directory)
can only be done with Apache. svnserve don't have any mechanism to do
fine-grained authorization. But authentication (which is what you
want) can be done with svnserve using a unique password file. I did a
test here and it worked fine. Under your repository's directory there
is a conf directory which contains a file called svnserve.conf. You
can put there the location of your password file which can be placed
into another directory (probably you will want to place it out of your
repo's directory). Your svnserve.conf file should look like this:

[general]
anon-access = none
auth-access = write
password-db = path/to/password/file

> I was thinking of adding my password text file automatically to s
> repository creating script (I think its possible).
> --
> Flapflap[at]sans-facon.net --
> DevBlog : http://www.kilooctet.net

Hope this helps,

Célio

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

Re: Question from a newbie...

[Célio Cidral Junior <cc...@gmail.com>]

Hi FlapFlap

2005/11/25, Flapflap <li...@sans-facon.net>:
> Hi there,
>
> Would like that  :
>
> 1- when somebody make an update, the file is automatically llock.

I think this is not possible.


> 2- when somebody commit is file it automatically will be unlock (i think
> it's all ready the case)

Yes, this is already the case.


> 3- when commit is file, is local version file be marked as read-only (I
> got Windows (TSVN) and Mac Os X (SVNX) clients)

I think this is not possible. Visual SourceSafe works just as you
stated above at 1, 2 and 3 (however I urge you NOT to use it if you
want "safe" source control).


> 4- all my repository (I'll make one by project) get the same use /
> password list so I don't have to copy it every time I create a new
> repository

You can do this using Apache HTTP server. Take a look at chapter six
(Server Configuration) of the book, in the section called
"Authorization Options":

http://svnbook.red-bean.com/nightly/en/svn.serverconfig.httpd.html

You can create only one authz file and use it for several
repositories. That's what we use here in my company


Celio Cidral Junior
WEG Eletric
http://www.weg.com.br

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