Re: F39 proposal: Changes of defaults in createrepo_c-1.0.0 (System-Wide Change proposal)

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



> - When adding groups.xml to repodata createrepo_c currently adds two
> variants to repomd.xml. The specified file as is, uncompressed, with
> the type "group" and also a compressed variant with type "group_XX",
> where XX is compression suffix. This is atypical and unexpected. We
> propose to include just one variant of groups.xml using specified
> compression and repomd.xml type "group". This is not compatible with
> yum in RHEL 7. If required users will still be able to create
> repositories with the old layout using modifyrepo_c.
> Further information: https://bugzilla.redhat.com/show_bug.cgi?id=2056318

If we're planning to drop by-default compatibility with EL7 anyway and bump to 1.0, we could go a little bit further.

* "createrepo_c" doesn't need to support sqlite metadata generation at all, so long as the repository producer can run "sqliterepo_c".  If I recall correctly, yum on EL7 doesn't actually need the sqlite metadata to be generated in any case, it can produce that metadata itself so long as it has the XML.  Making it available only avoids a local processing step.  But if "modifyrepo_c" will be necessary to work with most EL7 repos, then making "sqliterepo_c" necessary for a minor optimization isn't a big leap.

* createrepo_c currently has two different switches for compression types, "compress-type" and "general-compress-type", where the latter applies to everything and the former only applies to files that are *not* "primary", "filelists", and "other".  there should be one compression type option and it should be applied uniformly to all metadata produced by the "createrepo_c" tool.  Yum would have choked on this because of the special handling around "comps", but I believe it should no longer be a concern?
_______________________________________________
devel mailing list -- devel@xxxxxxxxxxxxxxxxxxxxxxx
To unsubscribe send an email to devel-leave@xxxxxxxxxxxxxxxxxxxxxxx
Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: https://lists.fedoraproject.org/archives/list/devel@xxxxxxxxxxxxxxxxxxxxxxx
Do not reply to spam, report it: https://pagure.io/fedora-infrastructure/new_issue




[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
[Index of Archives]     [Fedora Announce]     [Fedora Users]     [Fedora Kernel]     [Fedora Testing]     [Fedora Formulas]     [Fedora PHP Devel]     [Kernel Development]     [Fedora Legacy]     [Fedora Maintainers]     [Fedora Desktop]     [PAM]     [Red Hat Development]     [Gimp]     [Yosemite News]

  Powered by Linux