implementing the additional repo migrations
hi, this night i started taking a look at the extra repos that need to be migrated. many of them contain reconstructible, but large pdf files, that i'd like to kill off for saving space. this shouldn't be a problem as long as the svn that many people link to stays available read-only, but it would need a bit of a plan if that goes as well. im currently investigating what parts of extradoc are reconstructible it seems the most costly things are * the split + full variants of the eu report (no tex aviliable) * papers (also no tex available) * api_html.tar.gz * the talks directory the talks directory is the largest size offender as well as the tree that’s the hardest to figure out (in terms of what’s reconstructible and what not). (more details later) The language repo's seem to be mostly fine, except for the prolog one, which contains a few reconstructible pdf's regards Ronny
On 02/25/2011 10:36 PM, Ronny Pfannschmidt wrote:
this night i started taking a look at the extra repos that need to be migrated.
many of them contain reconstructible, but large pdf files, that i'd like to kill off for saving space.
this shouldn't be a problem as long as the svn that many people link to stays available read-only, but it would need a bit of a plan if that goes as well.
im currently investigating what parts of extradoc are reconstructible
it seems the most costly things are
* the split + full variants of the eu report (no tex aviliable) * papers (also no tex available) * api_html.tar.gz * the talks directory
the talks directory is the largest size offender as well as the tree that’s the hardest to figure out (in terms of what’s reconstructible and what not).
(more details later)
The language repo's seem to be mostly fine, except for the prolog one, which contains a few reconstructible pdf's
Don't worry about Prolog, that has been manually migrated already by me a while ago. Carl Friedrich
participants (2)
-
Carl Friedrich Bolz
-
Ronny Pfannschmidt