Re: [PATCH] use gzip compression with --no-name to create identicals steps backups

["Yann E. MORIN" <yann dot morin dot 1998 at anciens dot enib dot fr>]

Bruno, All,

On Saturday 20 March 2010 11:10:58 Bruno Tarquini wrote:
> Thanks for this long reply, and sorry for my bad language.

What bad language? ;-)

> > Oh! You mean you want to (hard|sym)link the tarballs when their contents
> > are the same, to save space, right?
> That was the idea, I used fdupes + some script to convert all duplicates to
> hardlinks:
[--SNIP--]
> === Total lost size ===
> 422485155

> That 's what I realized after, removing duplicates after the build is
> useless since all backups could simply be removed. And removing duplicates
> during the build process is far too complicated for a simple debug feature
> like you said.

Yep! :-)

> Ideally ct-NG should know about empty step and simply 
> clone the previous step, but it's more changes and I see no enough reasons
> to do it, excepts to show "skipping empty step" to users :-)

Yes. And those of us debugging crosstool-NG itself (and thus using the
backups per steps) are not legions. We can live with up to 1.5GiB of
temp data.

> > Just for information, here is the space it takes to store the backup
> > tarballs for the armeb-unknown-linux-gnueabi sample:
[--SNIP--]
> > Which means that the backup tarballs are just less than one third of the
> > total space used to build the toolchain (not counting the 450MiB used by
> > the toolchain itself, in which case the backup tarballs account for
> > roughly 1/4th of the total space).
> When you do minimalist build (no target tools...), you have lots of
> empty steps, so a more high duplicated backups ratio.

Yes, but again, that's just temp data that you can rip-off afterwards.

> In fact, I used them to create some kind of binary packages (by diffing
> each steps):
> linux-headers, libc... some i came manage to import them in a the target
> with a package manager.

That's absolutely not the purpose of those tarballs. What you really want
to package is the resulting toolchain. The bckup tarballs are only for
debug purposes.

> > Not needed. -3 is the default for gzip compression.
> Well, from man gzip and:
[--SNIP--]
> it seems to be -6 now.

Yes, you are absolutely right! My mistake. A tiring, loong day, and I write
non-sense. It always was -6. Sorry.

Wanna come with a patch to this effect, please?

Regards,
Yann E. MORIN.

-- 
.-----------------.--------------------.------------------.--------------------.
|  Yann E. MORIN  | Real-Time Embedded | /"\ ASCII RIBBON | Erics' conspiracy: |
| +33 662 376 056 | Software  Designer | \ / CAMPAIGN     |  ___               |
| +33 223 225 172 `------------.-------:  X  AGAINST      |  \e/  There is no  |
| http://ymorin.is-a-geek.org/ | _/*\_ | / \ HTML MAIL    |   v   conspiracy.  |
'------------------------------^-------^------------------^--------------------'



--
For unsubscribe information see http://sourceware.org/lists.html#faq