On Thu, 9 Apr 2020 at 17:58, Justin Forbes <jmforbes(a)linuxtx.org> wrote:
On Thu, Apr 9, 2020 at 10:41 AM Tomas Tomecek <ttomecek(a)redhat.com> wrote:
>
> On Thu, Apr 9, 2020 at 4:34 PM Jeremy Cline <jeremy(a)jcline.org> wrote:
> >
> > We actually are. I assume you're asking about why we're not using
> > packit. We're not on GitHub so the service isn't (as far as I can
tell)
> > useful to us. There's huge piles of existing bash scripts and makefiles
> > that achieve about what I think packit-the-cli would give us so it
> > would be some amount of work with no obvious benefit to move at the
> > moment. Generally speaking, though, I'm not against the idea.
>
> When we started packit, we played with the scripts and makefiles in
> your kernel repo and I hope it's not too bold of me to say that it
> shouldn't be that hard to integrate the two now.
>
> I'm assuming you're using pagure.io - at this point, we're not going
> to integrate packit with pagure (for obvious reasons). What are your
> future plans for the git forge?
>
> The benefits would be that you'd get all the features of packit which
> we have right now and those we implement in future.
>
While the scripts have changed a bit, I don't see any actual benefit
to packit with what we are doing. The script to create a release
builds the dist-git. This was more about managing the lookaside so
that we weren't uploading quite as much with the daily kernel builds
in rawhide.
I still recommend using the rpkg-preprocessor approach that I
suggested here or at least looking at the possibility to use it and
finding out what should be done so that it is useful for you.
I can cooperate on this with you. I am looking for some cooperation
for quite a long time.
The preprocessor has support for custom macros that you could use from
your spec file. These macros could hook into your already created
scripts. I admit I don't know your exact workflow but I firmly believe
you could find the tool valuable.
Best regards
clime
>
> Justin
> _______________________________________________
> infrastructure mailing list -- infrastructure(a)lists.fedoraproject.org
> To unsubscribe send an email to infrastructure-leave(a)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/infrastructure@lists.fedora...