On Wed, Apr 14, 2021 at 2:52 PM Vitaly Zaitsev via devel
<devel@lists.fedoraproject.org> wrote:
>
> On 14.04.2021 10:45, Tomas Tomecek wrote:
> > Our main goal in the SIG right now is to establish a development
> > workflow for Fedora Linux packages using repositories with sources and
> > upstream history (this is what we call source-git), instead of just
> > distribution files with links to tarballs (dist-git).
>
> Debian style with full local copies of repositories?
>
> I don't think this is a good idea, because I don't want to clone
> upstream repositories and store my SPECs in them.

Could you, please, be more constructive and say what the actual
problems are for you with such repositories?

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.

Thank you,

Tomas

> --
> Sincerely,
>    Vitaly Zaitsev (vit...@easycoding.org)
> _______________________________________________
> devel mailing list -- devel@lists.fedoraproject.org
> To unsubscribe send an email to devel-le...@lists.fedoraproject.org
> 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@lists.fedoraproject.org
> Do not reply to spam on the list, report it: 
> https://pagure.io/fedora-infrastructure
_______________________________________________
devel mailing list -- devel@lists.fedoraproject.org
To unsubscribe send an email to devel-le...@lists.fedoraproject.org
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@lists.fedoraproject.org
Do not reply to spam on the list, report it: 
https://pagure.io/fedora-infrastructure

Reply via email to