Subjects of discussion I can think of right now:
(poke @nddrylliog @fredreichbier @showstopper @duckinator @wandernauta )
Prior and interesting discussions:
You're all here debating but I've got uncommitted specifications for 'bottles' in my git repo. Wait till I push that :)
And yes, pkg-config is the minimum denominator. (There's pkg-config-lite for mingw32 if you don't want to deal with the glib shit). As far as packages go, I'm going with apt-get on Ubuntu, brew on OSX, and a custom solution on Win32 (no reliable package manager for libraries there...)
More details to follow.
And yes, coke will be able to produce self-sufficient 'distribution files' for each target. For Linux that probably means statically linked. For OSX that means dynamically linked, but with dylibbundler we can fix the executable and copy the dylibs so it'll look for them in the app bundle. For Windows it basically means.. a .zip files (or folder?) with the .exe and the right .dll(s) side by side.
Sure, why not. The way I have in mind allows integration with pretty much any 3rd party package manager.. I'll expand on that later. #famouslastwords
As of right now there are three things to read:
@wandernauta If you want to help with Arch support you can start right now by writing utils/pacman-status.sh, which should be very easy. Just take a look at utils/apt-status.sh and work from here, should be pretty straightforward.
Gentoo support is welcome as well! Those files will be piggy-backed into coke itself, and copied to the relevant directories when producing output.
@nddrylliog utils/pacman-status.sh is live
Discussion of features that are still at the idea level should take place in the wiki now: https://github.com/nddrylliog/rock/wiki/Tools - please summarize the feature there.
/cc @wandernauta @shamanas