On 14.04.2021 16:27, Tomas Tomecek wrote:
Could you, please, be more constructive and say what the actual problems are for you with such repositories?
1. Some upstream repositories (Qt, Chromium, Linux kernel) are very huge (more than 100 GiB). I don't want to download them from upstream and then upload to Fedora.
2. Keeping such huge repositories will take up a lot of disk space on the maintainer's computers.
3. Rebase problem. Maintainers will need do a manual rebase on every upstream release/commit. Rebasing to the next major version will be a serious problem for the projects with a lot of of downstream patches.
4. Some project have a weird git workflow between minor releases. I know at least one project that uses Git tags with cherry-picked and manually backported commits. Such detached tags cannot be merged into master branch without resolving merge conflicts.
5. Force pushes must be enabled, which is too dangerous IMO.
I understand that upstream repositories can have a long history - we could optimize and have shallow copies or only fetch recent upstream history if needed. Also, one would ideally only clone once and kept fetching new changes.
Do you want to force switch all Fedora packages to a new workflow? -- Sincerely, Vitaly Zaitsev (vitaly@xxxxxxxxxxxxxx) _______________________________________________ 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 on the list, report it: https://pagure.io/fedora-infrastructure
