pacfree | simple pacman wrapper written in Bash and aimed to make
kandi X-RAY | pacfree Summary
kandi X-RAY | pacfree Summary
pacfree is a Shell library. pacfree has no bugs, it has no vulnerabilities, it has a Strong Copyleft License and it has low support. You can download it from GitHub.
NOTE: Since version 0.4.0, most of the code have been rewritten and merged with pacrep functionality. I simply love pacman; but I think it falls short when it comes to free-software. It simply makes no distinction at all between free and non-free software; but it should. What I offer here is a simple pacman wrapper written in Bash and aimed to make pacman free-software aware by making use of Parabola's blacklists. The wrapper is very simple: every time the user attempts to install some package via the --sync (-S) option, the wrapper will check the blacklist looking for the package. If found, that is, if the package is non-free, the user will be warned and asked whether or not she wants to continue. Next, if necessary, pacman will be called to do its thing. This point is absolutely relevant: WARNING the user about proprietary software is one thing, and FORCING the user NOT to install proprietary sofware, as Parabola does (via its your-freedom package), is a completely different thing. No one can be FORCED to be free; that's impossible. Freedom must be chosen, and there is no freedom without choices. It is the user herself, and not someone else, be it a person or a software, who must freely DECIDE not to install proprietary software. Someone who is forced to do the right thing would be a good robot, a good machine, but not a good person. This is where Parabola, and all the FSF endorsed distributions as well, is wrong; and this is why I wrote this wrapper: it will warn you about non-free software, but it's up to you what to do about it. Once pacfree knows what is to be installed/upgraded, it checks every package against a rules list (a series of lines in the form "repo/pkg" defined in a rules file: $HOME/.config/pacfree/rules.conf), and, if a rule for the package is found, it installs the package from the specified repository (instead of from the first repository defined in /etc/pacman.conf providing the package, which is pacman's default behaviour). The main idea of this functionality is to make pacman able to handle packages with the same name in different repositories, for example, "core/licenses" and "libre/licenses", or "community/midori" and "libre/midori", without the need to explicitly specify the repository in the command line, besides the important fact that it works for upgrades as well. Just define in the rules file from which repository a certain package is to be installed/upgraded and pacfree will always install/upgrade the package from the specified repository (disregarding the repositories order in /etc/pacman.conf). In this way, we can use packages and repositories coming from different Arch based distributions more easily and smoothly. If you are concerned with free-software, just as I am, you don't need to move away from Arch: it is just too great to be left behind. Instead, you can help to make it even better, more free, and more powerful. This is the reason of this wrapper. Of course, it is far from perfect, but it's better than none.
NOTE: Since version 0.4.0, most of the code have been rewritten and merged with pacrep functionality. I simply love pacman; but I think it falls short when it comes to free-software. It simply makes no distinction at all between free and non-free software; but it should. What I offer here is a simple pacman wrapper written in Bash and aimed to make pacman free-software aware by making use of Parabola's blacklists. The wrapper is very simple: every time the user attempts to install some package via the --sync (-S) option, the wrapper will check the blacklist looking for the package. If found, that is, if the package is non-free, the user will be warned and asked whether or not she wants to continue. Next, if necessary, pacman will be called to do its thing. This point is absolutely relevant: WARNING the user about proprietary software is one thing, and FORCING the user NOT to install proprietary sofware, as Parabola does (via its your-freedom package), is a completely different thing. No one can be FORCED to be free; that's impossible. Freedom must be chosen, and there is no freedom without choices. It is the user herself, and not someone else, be it a person or a software, who must freely DECIDE not to install proprietary software. Someone who is forced to do the right thing would be a good robot, a good machine, but not a good person. This is where Parabola, and all the FSF endorsed distributions as well, is wrong; and this is why I wrote this wrapper: it will warn you about non-free software, but it's up to you what to do about it. Once pacfree knows what is to be installed/upgraded, it checks every package against a rules list (a series of lines in the form "repo/pkg" defined in a rules file: $HOME/.config/pacfree/rules.conf), and, if a rule for the package is found, it installs the package from the specified repository (instead of from the first repository defined in /etc/pacman.conf providing the package, which is pacman's default behaviour). The main idea of this functionality is to make pacman able to handle packages with the same name in different repositories, for example, "core/licenses" and "libre/licenses", or "community/midori" and "libre/midori", without the need to explicitly specify the repository in the command line, besides the important fact that it works for upgrades as well. Just define in the rules file from which repository a certain package is to be installed/upgraded and pacfree will always install/upgrade the package from the specified repository (disregarding the repositories order in /etc/pacman.conf). In this way, we can use packages and repositories coming from different Arch based distributions more easily and smoothly. If you are concerned with free-software, just as I am, you don't need to move away from Arch: it is just too great to be left behind. Instead, you can help to make it even better, more free, and more powerful. This is the reason of this wrapper. Of course, it is far from perfect, but it's better than none.
Support
Quality
Security
License
Reuse
Support
pacfree has a low active ecosystem.
It has 1 star(s) with 0 fork(s). There are no watchers for this library.
It had no major release in the last 12 months.
pacfree has no issues reported. There are no pull requests.
It has a neutral sentiment in the developer community.
The latest version of pacfree is v0.6.1
Quality
pacfree has no bugs reported.
Security
pacfree has no vulnerabilities reported, and its dependent libraries have no vulnerabilities reported.
License
pacfree is licensed under the GPL-2.0 License. This license is Strong Copyleft.
Strong Copyleft licenses enforce sharing, and you can use them when creating open source projects.
Reuse
pacfree releases are available to install and integrate.
Installation instructions are not available. Examples and code snippets are available.
Top functions reviewed by kandi - BETA
kandi's functional review helps you automatically verify the functionalities of the libraries and avoid rework.
Currently covering the most popular Java, JavaScript and Python libraries. See a Sample of pacfree
Currently covering the most popular Java, JavaScript and Python libraries. See a Sample of pacfree
pacfree Key Features
No Key Features are available at this moment for pacfree.
pacfree Examples and Code Snippets
No Code Snippets are available at this moment for pacfree.
Community Discussions
No Community Discussions are available at this moment for pacfree.Refer to stack overflow page for discussions.
Community Discussions, Code Snippets contain sources that include Stack Exchange Network
Vulnerabilities
No vulnerabilities reported
Install pacfree
You can download it from GitHub.
Support
For any new features, suggestions and bugs create an issue on GitHub.
If you have any questions check and ask questions on community page Stack Overflow .
Find more information at:
Reuse Trending Solutions
Find, review, and download reusable Libraries, Code Snippets, Cloud APIs from over 650 million Knowledge Items
Find more librariesStay Updated
Subscribe to our newsletter for trending solutions and developer bootcamps
Share this Page