Opened 12 years ago
Closed 12 years ago
#950 closed defect (fixed)
mini iso too big to fit into a 4GB USB stick
Reported by: | kalxas | Owned by: | |
---|---|---|---|
Priority: | major | Milestone: | OSGeoLive6.0RC1 |
Component: | OSGeoLive | Keywords: | 6.0 |
Cc: | live-demo@… |
Description
We are observing unusually large mini iso files. Especially the last beta3 build was not able to be completed due to size going over 4.4GB We have to debug remastersys since it seems to bring in lots of packages like akonadi etc.
Change History (6)
follow-up: 4 comment:1 by , 12 years ago
comment:2 by , 12 years ago
Milestone: | → OSGeoLive6.0RC1 |
---|
comment:3 by , 12 years ago
Is anything we care about making use of the sessioninstaller package?
Hamish
comment:4 by , 12 years ago
Replying to hamish:
rasdaman left behind a number of -dev packages in beta3, hopefully that is fixed now.
here's a conundrum: Things like QGIS, GRASS, and R have extension/addon managers to install extra packages. At least in the case of GRASS and R these can be compiled modules, which in turn can depend on having libproj-dev and libgdal(1)-dev installed.
Especially libgdal(1)-dev sucks in a whole host of other -dev pkg dependencies, all of which take up some room of their own.
We do ship libc6-dev and gcc etc to allow the disc to be generally used for e.g. stuck-in-an-airport development and further customization.
The addon extensions can make up a significant part of the community ecosystem. Do we get rid of all the geo-dev pacakges and save some disc space, or do we keep them, allow the building of addons, and try to recover the disc space elsewhere?
?, Hamish
I think it is useful to have development packages installed but perhaps those could be removed only for iso, since I don't think anyone would try to compile something from a live boot...
comment:5 by , 12 years ago
Priority: | blocker → major |
---|
Just completed build8234. After the latest changes done to shrink the iso, we now have 3.7G mini-iso. Great work all! I am going to bring md-system back to the next build so we can know where we are at full load.
Cheers, Angelos
comment:6 by , 12 years ago
Resolution: | → fixed |
---|---|
Status: | new → closed |
This is definitely fixed for 6.0beta4 (3.6G)
rasdaman left behind a number of -dev packages in beta3, hopefully that is fixed now.
here's a conundrum: Things like QGIS, GRASS, and R have extension/addon managers to install extra packages. At least in the case of GRASS and R these can be compiled modules, which in turn can depend on having libproj-dev and libgdal(1)-dev installed.
Especially libgdal(1)-dev sucks in a whole host of other -dev pkg dependencies, all of which take up some room of their own.
We do ship libc6-dev and gcc etc to allow the disc to be generally used for e.g. stuck-in-an-airport development and further customization.
The addon extensions can make up a significant part of the community ecosystem. Do we get rid of all the geo-dev pacakges and save some disc space, or do we keep them, allow the building of addons, and try to recover the disc space elsewhere?
?, Hamish