New comment by reback00 on void-packages repository

https://github.com/void-linux/void-packages/issues/25901#issuecomment-719965729

Comment:
@hippi777 
> otherwise the common ground for the templates could still be nice, but im also under educated about the requirements of this, and i hope i will catch up with things around here sooner than later :D

Sure. Let us know if we can help in anything.

Also, if you want to get a better idea of how we liberated packages, you can check [this](https://notabug.org/reback00/void-goodies/src/master/liberatedpkgs) out. Sorry for somewhat unclear documentation for some of the packages. I wrote them as a note to myself back then without thinking about others.

We had lots of help from Parabola's [blacklist](https://git.parabola.nu/blacklist.git/plain/blacklist.txt) project. It is big list of nonfree packages with reasons for which the package is considered nonfree by Parabola community. We then work on cleaning the package based on the issue they described. ([details on how to parse it here](https://github.com/ymir-linux/void-packages/issues/8))

Each package has (a) some changes in the `template` files compared to Void's original version and/or (b) some patch added to `patches` folder. `template` changes are minor. So if we can store a diff of the template and include the patches needed for liberating, we can skip the need to store a copy of the template file. We can just apply a patch when a new version comes along, for example. The source for the `libre` repo can just be a collection of patches.

I don't have a lot of experience with big collection of patches. Can it screw things up? Maybe. But this is the solution I have so far.

Also, we have a [`your-freedom`](https://notabug.org/reback00/void-goodies/src/master/srcpkgs/your-freedom) package that once installed, conflicts with nonfree packages, so that you can't accidentally install any nonfree packages! This can also be a great tool for freedom lovers living on Void.