Re: Huge /pool folder with 202 MB of debs in basic minimal live system.
On 14/01/12 02:09 PM, Michael . wrote:
What did I say that makes you assume that?
Because that's the simplest way in which a build can fail and produce
the results you've observed. Also, you failed to provide sufficient
detail to rule it out.
Maybe next time I'll write
down every minute detail in my email or
That could get tedious for both of us.
should I just place a copy of my
config tree in my email.
Yes. And that way we can independently confirm your results, too.
I have 2 package.list.binary that are supposed
to put things in /pool (I did this deliberately) the other file is a
package.list.chroot (while I never mentioned it specifically I assumed,
my fault, you would recognise I did this because I did the binary).
Btw, you never mentioned the actual names of any of the debs from main
that you saw. Do they bear any relation to the binaries installed on the
live image? Or perhaps to the things brought into the pool via the
contrib & non-free things you've included? Without seeing your config,
it's hard to guess ...
p.s. We did warn about this in the doc:
Yes you did, that is why I did it how I did it .
Good. Glad people are reading the doc. It encourages me to write more.
Btw I did another run last night changing --debian-installer in my auto
config file to live instead of true and that made the /pool/main folder
134.9 MB (very different to 190.6 MB) so the type of debian-installer
used can add nearly 60 MB on it's own (there is nothing in the doc that
mentions this).
"Debian is installed by fetching and installing .deb packages using
debootstrap or cdebootstrap, from the local media ...". Does this not
indicate some deb files are placed in the pool for the "Regular" installer?
'Installation will proceed in an identical fashion to the "Regular"
installation described above, but at the actual package installation
stage, instead of using debootstrap to fetch and install packages, the
live filesystem image is copied to the target.' And doesn't this state
that instead of fetching packages from the local media, the contents of
the image are used? The implication is by now obvious, that no .deb
files are needed.
I think there was a mail message to the list some time ago (years, I
think) that gave rough estimates of how much each install method adds. I
concede it would not hurt to state more explicitly expected sizes (at
least in ballpark figures). Feel free to file a wishlist bug so we don't
forget. Bonus points for including a patch. ;)
Ben
Reply to: