On Fri, Jul 03, 2015 at 05:38:25PM +0300, Andrei Borzenkov wrote:
On Fri, Jul 3, 2015 at 5:30 PM, Brüns, Stefan <Stefan.Bruens@rwth-aachen.de> wrote:
On Friday, July 03, 2015 06:47:24 Marcus Meissner wrote:
On Fri, Jul 03, 2015 at 12:07:42AM +0300, Andrei Dziahel wrote:
Hi list,
Great to see next snapshot, but it comes with a problem — is it is huge which may be the burden for users with less performant internet connection (say I've got 2.2G to download on primary desktop and 1.5G on secondary desktop/fileserver).
Can delta rpm building and publishing be enabled for Tumbleweed repositories? That would save not just bandwidth but also time of fellow Tumbleweed enthusiasts. Or, if there's concerns of any sort, make it opt-in so project owners could test-drive it before enabling it globally.
You probably saw that usually the changes are small.
As we changed the system compiler, all packages had to be rebuilt. delta rpms would not have made it significantly smaller, as a new major compiler version usually changes a lot of things.
Ciao, Marcus
By their very nature, noarch packages wont be affected by a compiler change.
Often, these are large packages (wallpapers, documentation with screenshots).
Often, the package contents do not change even for newer versions.
Please correct, if I am wrong.
The content of such package may still be generated at build time (like genrating font from some source format) and tool to do it may need to be compiled. In this case package probably has BuildRequires on gcc which will trigger rebuild (I think).
We cover a lot of unchanging packages using build-compare. If build-compare worked, the package would not get updated in a full rebuild scenario. Ciao, Marcus -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org