Closed reback00 closed 4 years ago
The main one I want to liberate is texlive-bin/the other texlive packages in that list and acpi-call, plus those you've listed.
@drake-newell Well, I haven't used them myself. So feel free to correct me.
texlive-bin
is kind of like a meta package on Void. It actually makes the path of actual texlive version installed to be available in $PATH
. The actual texlive package is on separate package, such as texlive2019-bin
, texlive2020-bin
. I've looked into texlive2020-bin
. Although it does not have "Arch Linux" branding the way Arch package has, but it does have mentions of "Void Linux" and "void" for a file called void.profile
.
Void Linux is not 100% libre. So, to be strictly libre I guess we can change these instances to Void Libre
or something? Is the name Void Libre
ok to be used for this project?
acpi_call-dkms
has dependencies of "linux-headers" on Arch which has been changed to "linux-libre-headers" on Parabola. Void package template does not mention "linux-headers", so I guess we can pass it as libre.
As a sidenote, this makes me think if we should distinguish the packages that are already libre in a different manner? Because we would tend to build all of them listed on allowlist.txt. But that's not necessary if they're already libre. That's why I opened #19.
@reback00 I'm not exactly sure about a name that includes the name Void. Michael Aldridge, one of the void contributors, was in the fosshost irc and suggested that we not use the word void because it is not affiliated with it. I can ask him about it specifically though.
@drake-newell I think he is right. It seems as if we are official part of the void team. In that case I think we should decide for a new name. I've opened a separate issue to discuss: #21
As you may know we have ~200 minor packages to liberate. [list] It's a lot, but hey, we have to start somewhere, right?
your-freedom
package.My list is as follows: