Peter Kümmel <[email protected]> writes: | On 20.11.2011 23:23, Lars Gullik Bjønnes wrote: >> Peter Kümmel<[email protected]> writes: >> >> | Currently we have 4800 files in trunk. >> | 1500 file are boost headers. These 1500 >> | files we never touch, but we check them out, >> | check them for changes, and so on. >> >> so? > | adding or removing files on a boost update, setting | the eol-sytle property.
Hmm. eol-style seems like a red herring. That should be solvable with .subversion settings. Or are there problems with this that I have not seen? adding/removing files on boost update: But you are not going to use the upstreams boost.tgz are you? So you will have to create a new one each time, a new release is out? > >> >> | It is simple to replace the files with one tar.gz >> | which will be extracted while the autogen.sh or cmake run. >>> >> | What do you think about replacing boost/boost >> | by boost/boost.tar.gz and attached patch? >> >> I think it makes life harder. >> > | The patch wasn't hard. > >> And what you do gain by this added complexity? > | I have to move around 1500 files less. That is just a number. How does that change anything? On bad effect you will get with i a tar.gz is unwanted size increase in subversion repository size. (one boost.tar.gz each time it is updated.) -- Lgb
