Re: subversion cross compile (arm)

2010-12-03 Thread Philip Martin
Takács András  writes:

> / # svn mkdir file:///var/svn/testrepo/xxx -m "aaa"
> fs_fs: [LINE 2082] calling svn_fs_fs__read_noderev
> fs_fs: [LINE 2140] calling read_rep_offsets '0 0 4 4
> 2d2977d1c96f487abe4a1e202dd03b4e'
> read_rep_offsets: [LINE 1947] '0 0 4 4 2d2977d1c96f487abe4a1e202dd03b4e'
> read_rep_offsets: [LINE 1956] '0'
> read_rep_offsets: [LINE 1973] '0'
> read_rep_offsets: [LINE 1984] '4'
> read_rep_offsets: [LINE 1995] '4'
> read_rep_offsets: [LINE 2009] '2d2977d1c96f487abe4a1e202dd03b4e'
> apr_file_open: '/var/svn/testrepo/db/transactions/0-0.txn/node.0.0'
> Call svn_fsfs__write_noderev in svn_fs_fs__put_node_revision [LINE 2390]
> svn_fsfs__write_noderev HEADER_TEXT
> rev 0
> offs 4618626049922564096
> size 4
> exp size 4
> md5 2d2977d1c96f487abe4a1e202dd03b4e
> svn_fsfs__write_noderev HEADER_TEXT OK

So here the file should contain the line

text: 0 0 4 4 2d2977d1c96f487abe4a1e202dd03b4e

> fs_fs: [LINE 2082] calling svn_fs_fs__read_noderev
> fs_fs: [LINE 2140] calling read_rep_offsets '0 4 4 531704 (null)'
> read_rep_offsets: [LINE 1947] '0 4 4 531704 (null)'

but here when you read the file you get the wrong data.  Is the file
corrupt or does the problem occur svn_fs_fs__read_noderev?

> read_rep_offsets: [LINE 1956] '0'
> read_rep_offsets: [LINE 1973] '4'
> read_rep_offsets: [LINE 1984] '4'
> read_rep_offsets: [LINE 1995] '531704'
> subversion/libsvn_fs_fs/fs_fs.c:2239: (apr_err=160004)
> svn: Corrupt node-revision '0.0.t0-0'
> subversion/libsvn_fs_fs/fs_fs.c:2006: (apr_err=160004)
> svn: Malformed text representation offset line in node-rev
> read_rep_offsets: apr_strtok #4 last_string '' string '0' str '(null)'
> strlen(str) 6 (APR_MD5_DIGESTS
> IZE*2) 32 revision 0 offset 4 size 0 expsize 4

-- 
Philip


Re: subversion cross compile (arm)

2010-12-03 Thread Takács András
2010/12/3 Philip Martin :
> Takács András  writes:
>
>> / # svn mkdir file:///var/svn/testrepo/xxx -m "aaa"
>> fs_fs: [LINE 2082] calling svn_fs_fs__read_noderev
>> fs_fs: [LINE 2140] calling read_rep_offsets '0 0 4 4
>> 2d2977d1c96f487abe4a1e202dd03b4e'
>> read_rep_offsets: [LINE 1947] '0 0 4 4 2d2977d1c96f487abe4a1e202dd03b4e'
>> read_rep_offsets: [LINE 1956] '0'
>> read_rep_offsets: [LINE 1973] '0'
>> read_rep_offsets: [LINE 1984] '4'
>> read_rep_offsets: [LINE 1995] '4'
>> read_rep_offsets: [LINE 2009] '2d2977d1c96f487abe4a1e202dd03b4e'
>> apr_file_open: '/var/svn/testrepo/db/transactions/0-0.txn/node.0.0'
>> Call svn_fsfs__write_noderev in svn_fs_fs__put_node_revision [LINE 2390]
>> svn_fsfs__write_noderev HEADER_TEXT
>> rev 0
>> offs 4618626049922564096
>> size 4
>> exp size 4
>> md5 2d2977d1c96f487abe4a1e202dd03b4e
>> svn_fsfs__write_noderev HEADER_TEXT OK
>
> So here the file should contain the line
>
> text: 0 0 4 4 2d2977d1c96f487abe4a1e202dd03b4e

This line is in /var/svn/testrepo/db/revs/0/0 file.
It is parsed correctly.

>
>> fs_fs: [LINE 2082] calling svn_fs_fs__read_noderev
>> fs_fs: [LINE 2140] calling read_rep_offsets '0 4 4 531704 (null)'
>> read_rep_offsets: [LINE 1947] '0 4 4 531704 (null)'
>
> but here when you read the file you get the wrong data.  Is the file
> corrupt or does the problem occur svn_fs_fs__read_noderev?

I don't know the internal mechanism of subversion, so I don't know
what is this second text representation.
I guess it is generated for the committing (next) revision.
The issue coming (I think) from this function: svn_fsfs__write_noderev
which is called from svn_fs_fs__put_node_revision

>
>> read_rep_offsets: [LINE 1956] '0'
>> read_rep_offsets: [LINE 1973] '4'
>> read_rep_offsets: [LINE 1984] '4'
>> read_rep_offsets: [LINE 1995] '531704'
>> subversion/libsvn_fs_fs/fs_fs.c:2239: (apr_err=160004)
>> svn: Corrupt node-revision '0.0.t0-0'
>> subversion/libsvn_fs_fs/fs_fs.c:2006: (apr_err=160004)
>> svn: Malformed text representation offset line in node-rev
>> read_rep_offsets: apr_strtok #4 last_string '' string '0' str '(null)'
>> strlen(str) 6 (APR_MD5_DIGESTS
>> IZE*2) 32 revision 0 offset 4 size 0 expsize 4
>
> --
> Philip
>


Re: subversion cross compile (arm)

2010-12-03 Thread Philip Martin
Takács András  writes:

> 2010/12/3 Philip Martin :
>> Takács András  writes:
>>
>>> / # svn mkdir file:///var/svn/testrepo/xxx -m "aaa"
>>> fs_fs: [LINE 2082] calling svn_fs_fs__read_noderev
>>> fs_fs: [LINE 2140] calling read_rep_offsets '0 0 4 4
>>> 2d2977d1c96f487abe4a1e202dd03b4e'
>>> read_rep_offsets: [LINE 1947] '0 0 4 4 2d2977d1c96f487abe4a1e202dd03b4e'
>>> read_rep_offsets: [LINE 1956] '0'
>>> read_rep_offsets: [LINE 1973] '0'
>>> read_rep_offsets: [LINE 1984] '4'
>>> read_rep_offsets: [LINE 1995] '4'
>>> read_rep_offsets: [LINE 2009] '2d2977d1c96f487abe4a1e202dd03b4e'
>>> apr_file_open: '/var/svn/testrepo/db/transactions/0-0.txn/node.0.0'
>>> Call svn_fsfs__write_noderev in svn_fs_fs__put_node_revision [LINE 2390]
>>> svn_fsfs__write_noderev HEADER_TEXT
>>> rev 0
>>> offs 4618626049922564096
>>> size 4
>>> exp size 4
>>> md5 2d2977d1c96f487abe4a1e202dd03b4e
>>> svn_fsfs__write_noderev HEADER_TEXT OK
>>
>> So here the file should contain the line
>>
>> text: 0 0 4 4 2d2977d1c96f487abe4a1e202dd03b4e
>
> This line is in /var/svn/testrepo/db/revs/0/0 file.
> It is parsed correctly.

The new file 
 '/var/svn/testrepo/db/transactions/0-0.txn/node.0.0'
should also contain that same line.  Does it?

>>> fs_fs: [LINE 2082] calling svn_fs_fs__read_noderev
>>> fs_fs: [LINE 2140] calling read_rep_offsets '0 4 4 531704 (null)'
>>> read_rep_offsets: [LINE 1947] '0 4 4 531704 (null)'
>>
>> but here when you read the file you get the wrong data.  Is the file
>> corrupt or does the problem occur svn_fs_fs__read_noderev?
>
> I don't know the internal mechanism of subversion, so I don't know
> what is this second text representation.
> I guess it is generated for the committing (next) revision.
> The issue coming (I think) from this function: svn_fsfs__write_noderev
> which is called from svn_fs_fs__put_node_revision

The problem appears to be the data in the transactions/0-0.txn/node.0.0
file.  Either it is getting corrupted when written to the file, or when
subsequently read from the file.

-- 
Philip


Re: How to use custom path for config file

2010-12-03 Thread Andy Levy
On Fri, Dec 3, 2010 at 02:50, Victor Engmark
 wrote:
> It would be very useful to be able to compile Subversion to use a different 
> path than /etc/subversion/config for the default configuration file. Is this 
> possible? I've also asked on ServerFault 
> .
>

Look at the next to last Global option in svn help .


Re: How to use custom path for config file

2010-12-03 Thread Victor Engmark
On Dec 3, 2010, at 12:33 PM, Andy Levy wrote:

> On Fri, Dec 3, 2010 at 02:50, Victor Engmark
>  wrote:
>> It would be very useful to be able to compile Subversion to use a different 
>> path than /etc/subversion/config for the default configuration file. Is this 
>> possible? I've also asked on ServerFault 
>> .
>> 
> 
> Look at the next to last Global option in svn help .

This would be even more useful as a compile option (for example the existing 
--sysconfdir), instead of at each run.

Cheers,
Victor

RE: How to use custom path for config file

2010-12-03 Thread Ludwig, Michael
> > Look at the next to last Global option in svn help .
> 
> This would be even more useful as a compile option (for 
> example the existing --sysconfdir), instead of at each run.

If it isn't a compile option, you can edit the source and compile.

Or on Linux, use a symlink from the default location to your
custom location.

Michael


Re: How to use custom path for config file

2010-12-03 Thread Stefan Sperling
On Fri, Dec 03, 2010 at 02:20:54PM +0100, Victor Engmark wrote:
> On Dec 3, 2010, at 12:33 PM, Andy Levy wrote:
> 
> > On Fri, Dec 3, 2010 at 02:50, Victor Engmark
> >  wrote:
> >> It would be very useful to be able to compile Subversion to use a 
> >> different path than /etc/subversion/config for the default configuration 
> >> file. Is this possible? I've also asked on ServerFault 
> >> .
> >> 
> > 
> > Look at the next to last Global option in svn help .
> 
> This would be even more useful as a compile option (for example the existing 
> --sysconfdir), instead of at each run.
> 

You can change this line in subversion/libsvn_subr/config_impl.h ...

#  define SVN_CONFIG__SYS_DIRECTORY   "/etc/subversion"

... and recompile.

We would happily accept patches that make this path configurable from
the configure script.

Stefan


Re: subversion cross compile (arm)

2010-12-03 Thread Takács András
The problems seems to be somewhere between the generation
(representation_string) and the writing of the
/var/svn/testrepo/db/transactions/0-0.txn/node.0.0 file.
The bugous string will be in the file.

I'll try to locate the bug at the weekend.

András



--
Takács András
Skype: wakoond
GTalk: wakoond
MSN: wako...@freestart.hu



2010/12/3 Philip Martin :
> Takács András  writes:
>
>> 2010/12/3 Philip Martin :
>>> Takács András  writes:
>>>
 / # svn mkdir file:///var/svn/testrepo/xxx -m "aaa"
 fs_fs: [LINE 2082] calling svn_fs_fs__read_noderev
 fs_fs: [LINE 2140] calling read_rep_offsets '0 0 4 4
 2d2977d1c96f487abe4a1e202dd03b4e'
 read_rep_offsets: [LINE 1947] '0 0 4 4 2d2977d1c96f487abe4a1e202dd03b4e'
 read_rep_offsets: [LINE 1956] '0'
 read_rep_offsets: [LINE 1973] '0'
 read_rep_offsets: [LINE 1984] '4'
 read_rep_offsets: [LINE 1995] '4'
 read_rep_offsets: [LINE 2009] '2d2977d1c96f487abe4a1e202dd03b4e'
 apr_file_open: '/var/svn/testrepo/db/transactions/0-0.txn/node.0.0'
 Call svn_fsfs__write_noderev in svn_fs_fs__put_node_revision [LINE 2390]
 svn_fsfs__write_noderev HEADER_TEXT
 rev 0
 offs 4618626049922564096
 size 4
 exp size 4
 md5 2d2977d1c96f487abe4a1e202dd03b4e
 svn_fsfs__write_noderev HEADER_TEXT OK
>>>
>>> So here the file should contain the line
>>>
>>> text: 0 0 4 4 2d2977d1c96f487abe4a1e202dd03b4e
>>
>> This line is in /var/svn/testrepo/db/revs/0/0 file.
>> It is parsed correctly.
>
> The new file
>  '/var/svn/testrepo/db/transactions/0-0.txn/node.0.0'
> should also contain that same line.  Does it?
>
 fs_fs: [LINE 2082] calling svn_fs_fs__read_noderev
 fs_fs: [LINE 2140] calling read_rep_offsets '0 4 4 531704 (null)'
 read_rep_offsets: [LINE 1947] '0 4 4 531704 (null)'
>>>
>>> but here when you read the file you get the wrong data.  Is the file
>>> corrupt or does the problem occur svn_fs_fs__read_noderev?
>>
>> I don't know the internal mechanism of subversion, so I don't know
>> what is this second text representation.
>> I guess it is generated for the committing (next) revision.
>> The issue coming (I think) from this function: svn_fsfs__write_noderev
>> which is called from svn_fs_fs__put_node_revision
>
> The problem appears to be the data in the transactions/0-0.txn/node.0.0
> file.  Either it is getting corrupted when written to the file, or when
> subsequently read from the file.
>
> --
> Philip
>


Re: subversion cross compile (arm)

2010-12-03 Thread Takács András
One more interesting addition:

The representation_string function is called from svn_fs_fs__write_noderev.
Here at the nodrerev->data_rep section I preinted out the revision,
offset, size, enpanded_size fields from the noderev->data_rep
structure:

rev 0
offs 4618629949752868864
size 4
exp size 4
md5 2d2977d1c96f487abe4a1e202dd03b4e

The offset seems to be quite high. Is it normal?

The next debug step is in the representation_string function. Before
calling the apr_psprintf function, I printed out again the fields:

rs rev 0
rs offs 4618628953320456192
rs size 4
rs exp size 4
rs md5 2d2977d1c96f487abe4a1e202dd03b4e

Compare the offs and the rs offs lines! The values are modified. How
I did a small test again, and before my debug lines in the
representation_string function, I did this:

rep->offset = 400;

The result:

rs rev 0
rs offs 4618629039219802512
rs size 4
rs exp size 4
rs md5 2d2977d1c96f487abe4a1e202dd03b4e

The offs field modified again, but this isn't 400!!! How

I think it is a memory corruption thing, but I don't know where to find it!


Thanks a lot every small idea!



András

--
Takács András
Skype: wakoond
GTalk: wakoond
MSN: wako...@freestart.hu



2010/12/3 Takács András :
> The problems seems to be somewhere between the generation
> (representation_string) and the writing of the
> /var/svn/testrepo/db/transactions/0-0.txn/node.0.0 file.
> The bugous string will be in the file.
>
> I'll try to locate the bug at the weekend.
>
> András
>
>
>
> --
> Takács András
> Skype: wakoond
> GTalk: wakoond
> MSN: wako...@freestart.hu
>
>
>
> 2010/12/3 Philip Martin :
>> Takács András  writes:
>>
>>> 2010/12/3 Philip Martin :
 Takács András  writes:

> / # svn mkdir file:///var/svn/testrepo/xxx -m "aaa"
> fs_fs: [LINE 2082] calling svn_fs_fs__read_noderev
> fs_fs: [LINE 2140] calling read_rep_offsets '0 0 4 4
> 2d2977d1c96f487abe4a1e202dd03b4e'
> read_rep_offsets: [LINE 1947] '0 0 4 4 2d2977d1c96f487abe4a1e202dd03b4e'
> read_rep_offsets: [LINE 1956] '0'
> read_rep_offsets: [LINE 1973] '0'
> read_rep_offsets: [LINE 1984] '4'
> read_rep_offsets: [LINE 1995] '4'
> read_rep_offsets: [LINE 2009] '2d2977d1c96f487abe4a1e202dd03b4e'
> apr_file_open: '/var/svn/testrepo/db/transactions/0-0.txn/node.0.0'
> Call svn_fsfs__write_noderev in svn_fs_fs__put_node_revision [LINE 2390]
> svn_fsfs__write_noderev HEADER_TEXT
> rev 0
> offs 4618626049922564096
> size 4
> exp size 4
> md5 2d2977d1c96f487abe4a1e202dd03b4e
> svn_fsfs__write_noderev HEADER_TEXT OK

 So here the file should contain the line

 text: 0 0 4 4 2d2977d1c96f487abe4a1e202dd03b4e
>>>
>>> This line is in /var/svn/testrepo/db/revs/0/0 file.
>>> It is parsed correctly.
>>
>> The new file
>>  '/var/svn/testrepo/db/transactions/0-0.txn/node.0.0'
>> should also contain that same line.  Does it?
>>
> fs_fs: [LINE 2082] calling svn_fs_fs__read_noderev
> fs_fs: [LINE 2140] calling read_rep_offsets '0 4 4 531704 (null)'
> read_rep_offsets: [LINE 1947] '0 4 4 531704 (null)'

 but here when you read the file you get the wrong data.  Is the file
 corrupt or does the problem occur svn_fs_fs__read_noderev?
>>>
>>> I don't know the internal mechanism of subversion, so I don't know
>>> what is this second text representation.
>>> I guess it is generated for the committing (next) revision.
>>> The issue coming (I think) from this function: svn_fsfs__write_noderev
>>> which is called from svn_fs_fs__put_node_revision
>>
>> The problem appears to be the data in the transactions/0-0.txn/node.0.0
>> file.  Either it is getting corrupted when written to the file, or when
>> subsequently read from the file.
>>
>> --
>> Philip
>>
>


Re: subversion cross compile (arm)

2010-12-03 Thread Philip Martin
Takács András  writes:

> One more interesting addition:
>
> The representation_string function is called from svn_fs_fs__write_noderev.
> Here at the nodrerev->data_rep section I preinted out the revision,
> offset, size, enpanded_size fields from the noderev->data_rep
> structure:
>
> rev 0
> offs 4618629949752868864

In hex: 4018AB78

> size 4
> exp size 4
> md5 2d2977d1c96f487abe4a1e202dd03b4e
>
> The offset seems to be quite high. Is it normal?
>
> The next debug step is in the representation_string function. Before
> calling the apr_psprintf function, I printed out again the fields:
>
> rs rev 0
> rs offs 4618628953320456192

in hex: 4018AA90

> rs size 4
> rs exp size 4
> rs md5 2d2977d1c96f487abe4a1e202dd03b4e
>

At a guess its a 32/64 bit issue.  Are you using 64 file offsets?

-- 
Philip


Searching A SVN Repo

2010-12-03 Thread Brian Brophy
I realize this is not directly related to SVN itself; however, I am 
hoping this community may have some suggestions.  If there is a more 
appropriate forum I should be engaging, please let me know.


We have a repo with over 125 GB of data, containing everything from 
source code to requirements documents, etc.  The repo is accessible via 
https.  We'd like to be able to search the contents of the repo.  A use 
case may be taking a phrase of interest, some text, and finding 
occurrences within the repo where this text resides (ie, within the 
actual source code or documents).


I have considered pointing something like a search appliance at the 
https interface and letting it crawl/spider/index the data.  That could 
be one option.


And yes, one could checkout/update the repo to search it, but at 125 GB 
and growing that is a cumbersome approach to do many client-side searches.


Would anyone have any other options?  Has anyone done something similar?

Thank you,
Brian


RES: Searching A SVN Repo

2010-12-03 Thread Luiz Guilherme Kimel
Try SVNQuery

http://svnquery.tigris.org/

;-)


-Mensagem original-
De: Brian Brophy [mailto:brianmbro...@gmail.com] 
Enviada em: sexta-feira, 3 de dezembro de 2010 13:07
Para: users@subversion.apache.org
Assunto: Searching A SVN Repo

I realize this is not directly related to SVN itself; however, I am 
hoping this community may have some suggestions.  If there is a more 
appropriate forum I should be engaging, please let me know.

We have a repo with over 125 GB of data, containing everything from 
source code to requirements documents, etc.  The repo is accessible via 
https.  We'd like to be able to search the contents of the repo.  A use 
case may be taking a phrase of interest, some text, and finding 
occurrences within the repo where this text resides (ie, within the 
actual source code or documents).

I have considered pointing something like a search appliance at the 
https interface and letting it crawl/spider/index the data.  That could 
be one option.

And yes, one could checkout/update the repo to search it, but at 125 GB 
and growing that is a cumbersome approach to do many client-side searches.

Would anyone have any other options?  Has anyone done something similar?

Thank you,
Brian



Re: Searching A SVN Repo

2010-12-03 Thread Les Mikesell

On 12/3/2010 10:07 AM, Brian Brophy wrote:

I realize this is not directly related to SVN itself; however, I am
hoping this community may have some suggestions. If there is a more
appropriate forum I should be engaging, please let me know.

We have a repo with over 125 GB of data, containing everything from
source code to requirements documents, etc. The repo is accessible via
https. We'd like to be able to search the contents of the repo. A use
case may be taking a phrase of interest, some text, and finding
occurrences within the repo where this text resides (ie, within the
actual source code or documents).

I have considered pointing something like a search appliance at the
https interface and letting it crawl/spider/index the data. That could
be one option.

And yes, one could checkout/update the repo to search it, but at 125 GB
and growing that is a cumbersome approach to do many client-side searches.

Would anyone have any other options? Has anyone done something similar?


The commercial fisheye product does this:
http://www.atlassian.com/software/fisheye/ and it has some other 
features - but it's not free.


You might be able to roll some kind of search out of htdig, perhaps 
pointing it at viewvc instead of the subversion view.


If you are mostly interested in the head version and mostly in code, you 
can point opengrok:

http://hub.opensolaris.org/bin/view/Project+opengrok/WebHome
at a checked out copy of a project and it will give you a search with 
linked cross-references between code definitions and references plus 
some support for accessing the version log.


--
  Les Mikesell
   lesmikes...@gmail.com


Re: subversion cross compile (arm)

2010-12-03 Thread Takács András
I checked my toolchain. It's using 32 bit file offsets.
I tried an other toolchain (ct-ng + eglibc). Same result. :(

--
Takács András
Skype: wakoond
GTalk: wakoond
MSN: wako...@freestart.hu



2010/12/3 Philip Martin :
> Takács András  writes:
>
>> One more interesting addition:
>>
>> The representation_string function is called from svn_fs_fs__write_noderev.
>> Here at the nodrerev->data_rep section I preinted out the revision,
>> offset, size, enpanded_size fields from the noderev->data_rep
>> structure:
>>
>> rev 0
>> offs 4618629949752868864
>
> In hex: 4018AB78
>
>> size 4
>> exp size 4
>> md5 2d2977d1c96f487abe4a1e202dd03b4e
>>
>> The offset seems to be quite high. Is it normal?
>>
>> The next debug step is in the representation_string function. Before
>> calling the apr_psprintf function, I printed out again the fields:
>>
>> rs rev 0
>> rs offs 4618628953320456192
>
> in hex: 4018AA90
>
>> rs size 4
>> rs exp size 4
>> rs md5 2d2977d1c96f487abe4a1e202dd03b4e
>>
>
> At a guess its a 32/64 bit issue.  Are you using 64 file offsets?
>
> --
> Philip
>


Re: subversion cross compile (arm)

2010-12-03 Thread Philip Martin
Philip Martin  writes:

> Takács András  writes:
>
>> The next debug step is in the representation_string function. Before
>> calling the apr_psprintf function, I printed out again the fields:
>>
>> rs rev 0
>> rs offs 4618628953320456192
>
> in hex: 4018AA90
>
>> rs size 4
>> rs exp size 4
>> rs md5 2d2977d1c96f487abe4a1e202dd03b4e
>>
>
> At a guess its a 32/64 bit issue.  Are you using 64 file offsets?

Obviously you are printing 64-bit offsets, so some part of your system
uses 64-bit offsets.  I think the problem is that some other part of
your system is only writing 32-bits into 64-bits of memory, and leaving
the higher 32-bits with random values.

-- 
Philip


Re: subversion cross compile (arm)

2010-12-03 Thread Philip Martin
Takács András  writes:

> I checked my toolchain. It's using 32 bit file offsets.
> I tried an other toolchain (ct-ng + eglibc). Same result. :(
>
> 2010/12/3 Philip Martin :
>> Takács András  writes:
>>
>>> Here at the nodrerev->data_rep section I preinted out the revision,
>>> offset, size, enpanded_size fields from the noderev->data_rep
>>> structure:
>>>
>>> rev 0
>>> offs 4618629949752868864
>>
>> In hex: 4018AB78

Here you are printing 64-bits, so some part of your system thinks that
apr_off_t is 64-bits.  How are apr_off_t and APR_HAS_LARGE_FILES defined
in apr.h?

-- 
Philip


Re: external file

2010-12-03 Thread Daniel Becroft
 On Sat, Dec 4, 2010 at 10:35 AM, Scott Yan  wrote:

>  Hi, djcbecroft:
>
>   Thanks very much for your reply , but I'm afraid that branches can't meet
> my request. Because when we make some change to any projects, we want the
> changes reflect to all other projects just as external does, but when I
> modify a file in a branch, other branches won't know that until I do a
> merge, so , that means if I modify a file in project1, I must goto project2
> to do a merge, and then project3, and then more, besides, we modify the
> files really frequently.
>

Please remember to Reply All to ensure the conversation stays on the list.

Maybe. You can use branches, and then use intra-repository file externals to
avoid merging the changes across.

Cheers,
Daniel B.


> Best Regards
> Scott.Yan
>
>
>
> > CC: users@subversion.apache.org
> > From: djcbecr...@gmail.com
> > Subject: Re: external file
> > Date: Thu, 2 Dec 2010 23:09:57 +1000
> > To: scott...@live.com
>
> >
> > On 02/12/2010, at 20:30, Scott Yan  wrote:
> >
> > > Hi,
> > >
> > > At first, thanks for your great works, but our company really need
> inter-repository file-externals feature which is not supported now, so , is
> there any plan to do this?
> > >
> > > Below is our situation:
> > > There are a dozen sub-factories in our company , and we develop our ERP
> system ourselves, because there are very much diffrences between factories,
> our project became a dozen versions, which means we have a dozen repositoies
> for all the projects.
> >
> > This scenario sound like you should probably have one repository with
> separate branches per version, rather than individual repositories. Then you
> wouldn't need externals at all.
> >
> > > Obviously, there are many files are equal in these projects, we must
> share them between projects, but it's very difficult to share the whole
> directory because of many reason such as:
> > > 1. We use VSS before, and VSS support file share between projects, so
> we didn't place share files in seperate folder.
> > > 2. Usually, when we add a new module to the system , the whole module
> is shared in all the projects, but factories will ask some special functions
> for their own request, and there will be more and more files are diffrent
> from other projects.
> > > 3. there are several files are placed at root directory.
> > >
> > > For clearer description, I'll demonstrate our situation:
> > > Suppose there are 3 projects
> > > Project1
> > > Project2
> > > Project3
> > >
> > > There is a "HRManagement" folder in all of them.
> > > There are 100 files in HRManagement folder, 30 of them are equal
> between Project1, Project2 and Project3, but the others are not equal.
> > >
> > > If we make a new folder names "Share" below HRManagement, and place the
> 30 files to it:
> > > HRManagement/Share/sharefile1
> > > HRManagement/Share/sharefile2
> > > HRManagement/Share/sharefile3
> > > ..
> > >
> > > Because we reference sharefile1 as "HRManagement/sharefile1" before, so
> we must search the whole project ( in face, in all the projects, Project1,
> Project2, and Project3) for the old reference , and then change to
> "HRManagement/Share/sharefile1".
> > > And, this is just for a single file! There are sharefile2,
> sharefile3,.. to do the same work, which is impossile at all.
> >
> > And if one of these shared files needed to be changed for a single
> version, you would have to undo all that work. Again, branches sound like a
> better fit.
> >
> > > Thanks for reading this , and I really hope you will add the feature
> ...
> > >
> > >
> > > Best Regards
> > > Scott.Yan
> > >
> > >
>