fund features

Comments, questions, bug reports, etc.
Posts: 31
Joined: Thu Aug 06, 2015 7:09 am

Re: fund features

Post by zipmagic » Fri Dec 28, 2018 12:00 am

Our first commercially funded contribution is nearing completion here:


@cadgis - what was it you needed done yourself?

Maybe we can help out...

Posts: 6
Joined: Wed Dec 19, 2018 1:45 pm

Re: fund features

Post by cadgis » Mon Jan 07, 2019 1:39 pm

Happy new year everyone,

we need a way to make diffs. Something like "wimapply archive.wim 4 different-from=1" where 1 and 4 are images and different-from would tell to take both new and modified files (in image 4 compared to image 1). If we do an update on the test computer and it appears to work after 2 weeks of testing and we want to deploy it, but it's just a .ini file that was tweaked or whatever, reapplying the GBs of the whole archive on over 100 computers is way too much strain for the network and it also erases the local modifications made. So with something like a cherry pick. You would keep all the local "commits" and only apply the diff between image x and image y.

Posts: 6
Joined: Wed Dec 19, 2018 1:45 pm

Re: fund features

Post by cadgis » Mon Jan 21, 2019 12:58 pm

@synchronicity Or maybe some hints where to go in the code for a feature like that. If it was Python, I would just add a "for glob in image1: if glob not in (image2+image3): extract glob" for a command like "wim apply archive.wim 1 different-from=2,3". I guess in C it's a but more convoluted, but shouldn't be that hard?

Posts: 3
Joined: Mon Feb 04, 2019 5:53 am

Re: fund features

Post by WithinRafael » Mon Feb 04, 2019 9:14 am

synchronicity wrote:
Sat Dec 22, 2018 4:43 am
Yes, I just don't have as much time for wimlib anymore, what with a full time job and more important open source projects to work on. I'd like for more developers to get involved with wimlib. But indeed, for someone to make meaningful contributions they need to actually be qualified and not just some random person hired on a freelance programmers website.

There isn't documentation for developing wimlib per se, beyond the instructions for how to build it. But I think an actually good developer, especially one experienced with C programming and filesystems, could figure most things out pretty well. I've tried to make things clean and logical, follow established conventions, and leave helpful comments.

Logistics-wise, I don't currently list an official way to submit patches for review. But if someone were actually to be doing substantial, genuinely good work I'd be glad to arrange to review and/or apply patches via email, Github, or any other way that makes sense.

Unfortunately I don't think wimlib is widely used enough for a foundation to provide adequate funding. Even open source projects that are much more essential, e.g. zlib and OpenSSL, tend to be very underfunded.

So I'm afraid that if you can't convince me to implement your feature soon enough (considering that due to limited time I have to prioritize based on how many people want the feature, how easy it is including the future maintenance cost, whether reasonable arguments exist that the feature request is misguided, and other factors), the best hope is probably to take it up yourself. And if you have questions I'd encourage you to post them here on the forums, where you might be able to get some other people involved too.
It's not very easy for other devs to get involved here, have you considered uploading to GitHub/GitLab?

Site Admin
Posts: 292
Joined: Sun Aug 02, 2015 10:31 pm

Re: fund features

Post by synchronicity » Sat Feb 09, 2019 9:34 pm

It's not very easy for other devs to get involved here, have you considered uploading to GitHub/GitLab?
To reduce the barrier to entry I just went ahead and uploaded the source to Github here. So people can create pull requests there if they want. (And I will keep it in sync with the repo here at git://

Post Reply