Some of those libraries could also be build from source using Craft, the are
part of the win32libs category (which might need a rename), currently we
recommend to blacklist the category and receive prebuilds from your distro
.More packages could of course be added but for historical reasons we only
provide the dev-util category currently only on Windows.
The unix support in Craft is rather new and was only merged back rather
recently.
Why to use Craft on Mac?I think with Kraft we have a focused cross platform
source of packages, we should join forces and not try to do something different
on each and every platform. Using Craft we can ensure that we have up to date
recipes on all platforms. The cross platform availability of Craft is also an
argument for the developers who want to provide packages for their application
them self, they don't have to learn 10 tools but only one.
Ceers,
Hannah
> Subject: Re: KDE Emerge emerged as Craft
> From: mk-li...@mailbox.org
> Date: Mon, 21 Nov 2016 21:43:16 +0100
> CC: rjvber...@gmail.com; vonr...@kde.org; scarlett.gately.cl...@gmail.com;
> bcooks...@kde.org
> To: kde-...@kde.org
>
> Hi René,
>
> On 21 Nov 2016, at 11:54 , René J.V. Bertin <rjvber...@gmail.com> wrote:
>
> > Nice news! Could you summarise in a few words what kind of Mac-specific
> > advantages this build and package management system apports over existing
> > alternatives (Fink, HomeBrew, MacPorts, pkgsrc, possibly others)?
>
> Did you read what Hannah’s link [2] lists as dependency for Craft?
>
> Homebrew!
>
> Whew…
>
> Well, all of this:
>
> brew install cmake wget coreutils p7zip gettext ninja python3 cmake
> ninja p7zip bison boost shared-mime-info
>
> can also easily be installed via MacPorts.
>
>
> Funny, how Craft has been under our radar, not even the CI team has seen this
> coming, I am afraid... :)
>
> @Hannah, thanks for posting!!!
>
> Greets,
> Marko
>
