Home_greyopenFATE - openSUSE feature tracking > #302354
Dashboard | Search | Sign up | Login

Please login or register to be able to edit or vote this feature.

Split metadata by architecture / modules

Feature state

Rejected Information
Rejected Information
Rejected Information
Rejected Information


All packages are in a single file no matter if they are from different architectures, therefore ZYpp has to download everything

Any kind of metadata should be separated by architecture. ZYpp does it for patterns in 10.3, but it is still missing for packages

The metadata should be ideally separated by subdirectories and modules.

See references on how debian does it





icons/user_comment.png D. M. wrote: (10 years ago)

This is not true, YaST filter patterns in 10.3. Will edit the feature to represent the real problems

icons/user_comment.png F. L. wrote: (10 years ago)

Duncan, do we still need this / have an advantage from it ? if so, lets make it Mandatory.

icons/user_comment.png D. M. wrote: (10 years ago)

This feature requires:

- separate primary.xml files per architecture. 90% effort -> rudi , adrian

- tell libzypp to ignore certain pattern or convention ( primary-x86_64.xml ??? ) when downloading -> one liner.

It is not much benefit anymore as we are much faster now, but I would recommend pset it to desirable and pass to Rudi and Adrian.

icons/user_comment.png S. V. wrote: (10 years ago)

Adrian, this is something for you.

icons/user_comment.png A. S. wrote: (9 years ago)

We have seperate ppc from i586/x86_64 to reduce size.

We do not have seperation of meta data yet, but it would not help much anyway, as long as we have no filter on rebuild. All files would change anyway, so the size would be the same. It would actually slow down the process due to multiple downloads.

Last change: 8 years ago
Score: 2
  • Negative: 0
  • Neutral: 1
  • Positive: 2
Feature Export
Application-xmlXML   Text-x-logPlaintext   PrinterPrint