The recipes would be pulled in by a recipe so not complicated on the usage side.
I also thought about using multiple sources for recipes, but I guess things could become even more complicated that way. But what I see is, if we want to evolve Craft we need to reach out to non KDE devs. On 23/08/2017 16:38, laurent Montel wrote: > Hi, > Really I don't think it's a good think. > It's very easy to contribute to craft recipe on git kde > > It's too bad to have another access for develop recipe for kde. > > How we will get recipe now ? > We need to download on 2 different repo ? > > So if it's the case why we don"t have a repo kde + a repo for other apps in > githup ? > > Regards > > Le mercredi 23 août 2017, 15:33:09 CEST Hannah von Reth a écrit : >> Hi everyone, >> >> We have been thinking about splitting the Craft recipes into a separate >> repository for some time now. >> To have a Craft core and the recipes separated would enable us to >> provide more stable user experience. It would allow us to use the latest >> recipes with the stable core. >> >> At the same time Craft tries to get rid of the image as the KDE Windows >> build tool. >> >> Craft offers recipes for many libraries and non KDE applications. >> Additionally Craft offers support for Mac, Linux and FreeBSD. >> >> In order to reach more people we intend to move the recipes to GitHub to >> enable non KDE contributors to add their recipes. >> Craft would continue to be a KDE Project on the KDE infrastructure, only >> the recipes would move. >> >> >> Cheers, >> >> Hannah >
signature.asc
Description: OpenPGP digital signature
