On Wed, May 6, 2020 at 11:31 AM Vít Ondruch <vondruch(a)redhat.com> wrote:
This is a bit of irony:
~~~
post-upstream-clone:
- curl -O
https://src.fedoraproject.org/rpms/python3/raw/master/f/python3.spec
- curl -O
https://src.fedoraproject.org/rpms/python3/raw/master/f/idle3.appdata.xml
- curl -O
https://src.fedoraproject.org/rpms/python3/raw/master/f/idle3.desktop
- curl -O
https://src.fedoraproject.org/rpms/python3/raw/master/f/check-pyc-timesta...
# packit will apply the patches itself
- sed '/^Patch/d' -i python3.spec
# patckit uses %autosetup - and yes, the line below doesn't make sense
given
# how python3's spec look, this is just a demonstration of packit's
functionality
- sed '/^%patch/d' -i python3.spec
~~~
So why does not Packit do this by itself? Just the `curl -O
https://src.fedoraproject.org/rpms/python3/raw/master/f/python3.spec`
should be kept in some form ....
Vít
Víťo, you are getting off track here. I'd love to focus the discussion
around dist-git and source-git workflows, not talking about the
internals of how packit works. If you want to discuss such topic,
please start a new thread, or even better, open an upstream issue [1]
and we can have the discussion there.
[1]
https://github.com/packit-service/packit/issues/new
Thank you,
Tomas