move source tarballs out of the scm

classic Classic list List threaded Threaded
6 messages Options
Reply | Threaded
Open this post in threaded view
|

move source tarballs out of the scm

Hans-Joachim Lankenau
hi!

since the external source tarballs (e.g. boost/download/*) add their
size to the repository each time a new version is committed, it's one of
the major sources of the growth of the repository.

the cws ause110 implements a different approach to deal with these large
binary files:

- a file named ooo.lst lists the tarballs required for that specific
source version with the first line being the URL where to find them

- the sh script fetch_tarballs.sh knows how to fetch these files via
http and places them in a directory TARFILE_LOCATION, by default
"ext_sources" beside the repository

- when building, dmake knows where to get them by looking at the
environment variable TARFILE_LOCATION

if not disabled by the configure switch "--disable-fetch-external", the
bootstrap step updates TARFILE_LOCATION according to ooo.lst.
using "--with-external-tar" sets TARFILE_LOCATION to a place of own choice.

that's the idea, comments welcome...


tschau...

ause


---------------------------------------------------------------------
To unsubscribe, e-mail: [hidden email]
For additional commands, e-mail: [hidden email]

Reply | Threaded
Open this post in threaded view
|

Re: move source tarballs out of the scm

stephan.bergmann
On 01/28/10 18:26, Hans-Joachim Lankenau - Sun Microsystems Germany wrote:

> hi!
>
> since the external source tarballs (e.g. boost/download/*) add their
> size to the repository each time a new version is committed, it's one of
> the major sources of the growth of the repository.
>
> the cws ause110 implements a different approach to deal with these large
> binary files:
>
> - a file named ooo.lst lists the tarballs required for that specific
> source version with the first line being the URL where to find them
>
> - the sh script fetch_tarballs.sh knows how to fetch these files via
> http and places them in a directory TARFILE_LOCATION, by default
> "ext_sources" beside the repository
>
> - when building, dmake knows where to get them by looking at the
> environment variable TARFILE_LOCATION
>
> if not disabled by the configure switch "--disable-fetch-external", the
> bootstrap step updates TARFILE_LOCATION according to ooo.lst.
> using "--with-external-tar" sets TARFILE_LOCATION to a place of own choice.
>
> that's the idea, comments welcome...

Default TARFILE_LOCATION ("'ext_sources' beside the repository") should
probably not point outside the build directory (i.e., the source
directory, as the OOo build environment is not able to distinguish those
two; "build directory" and "source directory" being used with their GNU
autotools meaning here).

-Stephan

---------------------------------------------------------------------
To unsubscribe, e-mail: [hidden email]
For additional commands, e-mail: [hidden email]

Reply | Threaded
Open this post in threaded view
|

Re: move source tarballs out of the scm

Hans-Joachim Lankenau - Sun Germany - ham02 - Hamburg
In reply to this post by Hans-Joachim Lankenau
hi!

short reminder. ause110 is now approved and will hopefully be integrated
to DEV300 soon.

see also the added paragraph at
http://wiki.services.openoffice.org/wiki/Build_Environment_Effort/External_source_tarballs#Where_are_those_tarballs.3F

tschau...

ause

On 01/28/10 06:26 PM, Hans-Joachim Lankenau - Sun Microsystems Germany
wrote:

> hi!
>
> since the external source tarballs (e.g. boost/download/*) add their
> size to the repository each time a new version is committed, it's one of
> the major sources of the growth of the repository.
>
> the cws ause110 implements a different approach to deal with these large
> binary files:
>
> - a file named ooo.lst lists the tarballs required for that specific
> source version with the first line being the URL where to find them
>
> - the sh script fetch_tarballs.sh knows how to fetch these files via
> http and places them in a directory TARFILE_LOCATION, by default
> "ext_sources" beside the repository
>
> - when building, dmake knows where to get them by looking at the
> environment variable TARFILE_LOCATION
>
> if not disabled by the configure switch "--disable-fetch-external", the
> bootstrap step updates TARFILE_LOCATION according to ooo.lst.
> using "--with-external-tar" sets TARFILE_LOCATION to a place of own choice.
>
> that's the idea, comments welcome...
>
>
> tschau...
>
> ause
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: [hidden email]
> For additional commands, e-mail: [hidden email]
>
>

---------------------------------------------------------------------
To unsubscribe, e-mail: [hidden email]
For additional commands, e-mail: [hidden email]

Reply | Threaded
Open this post in threaded view
|

Re: move source tarballs out of the scm

stephan.bergmann
In reply to this post by stephan.bergmann
On 01/28/10 19:14, Stephan Bergmann wrote:

> On 01/28/10 18:26, Hans-Joachim Lankenau - Sun Microsystems Germany wrote:
>> hi!
>>
>> since the external source tarballs (e.g. boost/download/*) add their
>> size to the repository each time a new version is committed, it's one of
>> the major sources of the growth of the repository.
>>
>> the cws ause110 implements a different approach to deal with these large
>> binary files:
>>
>> - a file named ooo.lst lists the tarballs required for that specific
>> source version with the first line being the URL where to find them
>>
>> - the sh script fetch_tarballs.sh knows how to fetch these files via
>> http and places them in a directory TARFILE_LOCATION, by default
>> "ext_sources" beside the repository
>>
>> - when building, dmake knows where to get them by looking at the
>> environment variable TARFILE_LOCATION
>>
>> if not disabled by the configure switch "--disable-fetch-external", the
>> bootstrap step updates TARFILE_LOCATION according to ooo.lst.
>> using "--with-external-tar" sets TARFILE_LOCATION to a place of own
>> choice.
>>
>> that's the idea, comments welcome...
>
> Default TARFILE_LOCATION ("'ext_sources' beside the repository") should
> probably not point outside the build directory (i.e., the source
> directory, as the OOo build environment is not able to distinguish those
> two; "build directory" and "source directory" being used with their GNU
> autotools meaning here).

...and should thus be added to .hgignore

> -Stephan


---------------------------------------------------------------------
To unsubscribe, e-mail: [hidden email]
For additional commands, e-mail: [hidden email]

Reply | Threaded
Open this post in threaded view
|

Re: move source tarballs out of the scm

Hans-Joachim Lankenau
hi!

Stephan Bergmann wrote:

> On 01/28/10 19:14, Stephan Bergmann wrote:
>> On 01/28/10 18:26, Hans-Joachim Lankenau - Sun Microsystems Germany
>> wrote:
>>> hi!
>>>
>>> since the external source tarballs (e.g. boost/download/*) add their
>>> size to the repository each time a new version is committed, it's one of
>>> the major sources of the growth of the repository.
>>>
>>> the cws ause110 implements a different approach to deal with these large
>>> binary files:
>>>
>>> - a file named ooo.lst lists the tarballs required for that specific
>>> source version with the first line being the URL where to find them
>>>
>>> - the sh script fetch_tarballs.sh knows how to fetch these files via
>>> http and places them in a directory TARFILE_LOCATION, by default
>>> "ext_sources" beside the repository
>>>
>>> - when building, dmake knows where to get them by looking at the
>>> environment variable TARFILE_LOCATION
>>>
>>> if not disabled by the configure switch "--disable-fetch-external", the
>>> bootstrap step updates TARFILE_LOCATION according to ooo.lst.
>>> using "--with-external-tar" sets TARFILE_LOCATION to a place of own
>>> choice.
>>>
>>> that's the idea, comments welcome...
>>
>> Default TARFILE_LOCATION ("'ext_sources' beside the repository")
>> should probably not point outside the build directory (i.e., the
>> source directory, as the OOo build environment is not able to
>> distinguish those two; "build directory" and "source directory" being
>> used with their GNU autotools meaning here).
>
> ..and should thus be added to .hgignore
[...]

in the long run i'd like clean up the repository and have something like
"build directory" and "source directory". first step for me in this
direction is not to add even more stuff that's written into the repository.

tschau...

ause

---------------------------------------------------------------------
To unsubscribe, e-mail: [hidden email]
For additional commands, e-mail: [hidden email]

Reply | Threaded
Open this post in threaded view
|

Re: move source tarballs out of the scm

stephan.bergmann
On Apr 1, 2010, at 6:40 PM, Hans-Joachim Lankenau wrote:
> in the long run i'd like clean up the repository and have something like "build directory" and "source directory".

me too

> first step for me in this direction is not to add even more stuff that's written into the repository.

understood

-Stephan

---------------------------------------------------------------------
To unsubscribe, e-mail: [hidden email]
For additional commands, e-mail: [hidden email]