├── .github ├── ISSUE_TEMPLATE │ ├── add-a-package-manager.md │ └── bug_report.md └── workflows │ ├── Install-and-test-MACOS.yml │ ├── Release-Tester.yml │ ├── Test-Update-Install-Linux.yml │ ├── Test-on-RPi.yml │ ├── deb-builder.yml │ └── update2deb.yml ├── CODE_OF_CONDUCT.md ├── LICENSE ├── README.md ├── debian ├── control ├── postinst └── postrm ├── images ├── update_simple-100x100.png └── update_simple.png ├── install ├── rpm ├── README.md ├── build.sh └── update.spec └── update /.github/ISSUE_TEMPLATE/add-a-package-manager.md: -------------------------------------------------------------------------------- 1 | --- 2 | name: Add a package manager 3 | about: If you have a package manager you would like to add, or get added, this is 4 | the right template for you. 5 | title: '' 6 | labels: package manager request 7 | assignees: '' 8 | 9 | --- 10 | 11 | Do you think a lot of users would find this package manager useful? 12 | 13 | If you have created a version of Update that has your suggested changes, upload it here. 14 | -------------------------------------------------------------------------------- /.github/ISSUE_TEMPLATE/bug_report.md: -------------------------------------------------------------------------------- 1 | --- 2 | name: Bug report 3 | about: Create a report to help us improve 4 | title: '' 5 | labels: '' 6 | assignees: '' 7 | 8 | --- 9 | 10 | **Describe the bug** 11 | A clear and concise description of what the bug is. 12 | 13 | **To Reproduce** 14 | Steps to reproduce the behavior: 15 | 1. Go to '...' 16 | 2. Click on '....' 17 | 3. Scroll down to '....' 18 | 4. See error 19 | 20 | **Expected behavior** 21 | A clear and concise description of what you expected to happen. 22 | 23 | **Screenshots** 24 | If applicable, add screenshots to help explain your problem. 25 | 26 | **Desktop (please complete the following information):** 27 | - OS: [e.g. iOS] 28 | - Browser [e.g. chrome, safari] 29 | - Version [e.g. 22] 30 | 31 | **Smartphone (please complete the following information):** 32 | - Device: [e.g. iPhone6] 33 | - OS: [e.g. iOS8.1] 34 | - Browser [e.g. stock browser, safari] 35 | - Version [e.g. 22] 36 | 37 | **Additional context** 38 | Add any other context about the problem here. 39 | -------------------------------------------------------------------------------- /.github/workflows/Install-and-test-MACOS.yml: -------------------------------------------------------------------------------- 1 | # This is a basic workflow to help you get started with Actions 2 | 3 | name: macOS_install_test 4 | 5 | # Controls when the workflow will run 6 | on: 7 | # Allows you to run this workflow manually from the Actions tab 8 | workflow_dispatch: 9 | 10 | # A workflow run is made up of one or more jobs that can run sequentially or in parallel 11 | jobs: 12 | # This workflow contains a single job called "build" 13 | install: 14 | # The type of runner that the job will run on 15 | runs-on: macos-latest 16 | 17 | # Steps represent a sequence of tasks that will be executed as part of the job 18 | steps: 19 | 20 | # Runs a set of commands using the runners shell 21 | - name: Install Update 22 | run: | 23 | brew install gnu-which 24 | curl "https://raw.githubusercontent.com/Crilum/update-app-script/main/install-macos" | sudo bash 25 | echo "Here is where Update is:" 26 | gwhich update 27 | - name: Test Update 28 | run: | 29 | update help 30 | update homebrew 31 | -------------------------------------------------------------------------------- /.github/workflows/Release-Tester.yml: -------------------------------------------------------------------------------- 1 | # This is a basic workflow to help you get started with Actions 2 | 3 | name: "Release Tester" 4 | 5 | # Controls when the workflow will run 6 | on: 7 | release: 8 | types: [released , prereleased, published] 9 | workflow_dispatch: 10 | 11 | # A workflow run is made up of one or more jobs that can run sequentially or in parallel 12 | jobs: 13 | # This workflow contains a single job called "build" 14 | Release-Test-Linux: 15 | # The type of runner that the job will run on 16 | runs-on: ubuntu-latest 17 | 18 | # Steps represent a sequence of tasks that will be executed as part of the job 19 | steps: 20 | # Runs a set of commands using the runners shell 21 | - name: "Install Update" 22 | run: | 23 | echo "Running install script..." 24 | curl "https://raw.githubusercontent.com/Crilum/update/main/install" | sudo bash 25 | echo "Here is where Update is:" 26 | which update 27 | - name: "Test Update" 28 | run: | 29 | echo "Running update..." 30 | update help 31 | update -u 32 | update -a 33 | Release-Test-MacOS: 34 | # The type of runner that the job will run on 35 | runs-on: macos-latest 36 | 37 | # Steps represent a sequence of tasks that will be executed as part of the job 38 | steps: 39 | # Runs a set of commands using the runners shell 40 | - name: "Run MacOS test" 41 | run: | 42 | brew install gnu-which 43 | echo "Running install script..." 44 | curl "https://raw.githubusercontent.com/Crilum/update/main/install-macos" | sudo bash 45 | echo "Here is where Update is:" 46 | gwhich update 47 | - name: "Test Update" 48 | run: | 49 | echo "Running update..." 50 | update help 51 | update -u 52 | update -H 53 | #Release-Test-RPi: 54 | # # The type of runner that the job will run on 55 | # runs-on: [self-hosted, linux, ARM64] 56 | # # Steps represent a sequence of tasks that will be executed as part of the job 57 | # steps: 58 | # # Runs a set of commands using the runners shell 59 | # - name: "Run Linux test" 60 | # run: | 61 | # echo "Running install script..." 62 | # curl "https://raw.githubusercontent.com/Crilum/update-app-script/main/install" | sudo bash 63 | # echo "Here is where Update is:" 64 | # which update 65 | # - name: "Test Update" 66 | # run: | 67 | # echo "Running update..." 68 | # update help 69 | # update 70 | -------------------------------------------------------------------------------- /.github/workflows/Test-Update-Install-Linux.yml: -------------------------------------------------------------------------------- 1 | # This is a basic workflow to help you get started with Actions 2 | 3 | name: "Test Update Install" 4 | # Controls when the workflow will run 5 | on: 6 | # Allows you to run this workflow manually from the Actions tab 7 | workflow_dispatch: 8 | 9 | jobs: 10 | # A workflow run is made up of one or more jobs that can run sequentially or in parallel 11 | Test_Update_Install: 12 | # The type of runner that the job will run on 13 | runs-on: ubuntu-latest 14 | 15 | # Steps represent a sequence of tasks that will be executed as part of the job 16 | steps: 17 | - name: Install Update 18 | run: | 19 | curl "https://raw.githubusercontent.com/Crilum/update-app-script/main/install" | sudo bash 20 | echo "Here is where Update is:" 21 | which update 22 | - name: Test Update 23 | run: | 24 | update help 25 | update -a 26 | -------------------------------------------------------------------------------- /.github/workflows/Test-on-RPi.yml: -------------------------------------------------------------------------------- 1 | name: Test-on-RPi 2 | 3 | # Controls when the workflow will run 4 | on: 5 | # Allows you to run this workflow manually from the Actions tab 6 | workflow_dispatch: 7 | 8 | # A workflow run is made up of one or more jobs that can run sequentially or in parallel 9 | jobs: 10 | Test-install-on-RPi: 11 | # The type of runner that the job will run on 12 | runs-on: [self-hosted, linux, ARM64] 13 | 14 | # Steps represent a sequence of tasks that will be executed as part of the job 15 | steps: 16 | 17 | # Runs a set of commands using the runners shell 18 | - name: Install Update 19 | run: | 20 | curl "https://raw.githubusercontent.com/Crilum/update-app-script/main/install" | sudo bash 21 | echo "Here is where Update is:" 22 | which update 23 | - name: Test Update 24 | run: | 25 | update help 26 | update 27 | 28 | -------------------------------------------------------------------------------- /.github/workflows/deb-builder.yml: -------------------------------------------------------------------------------- 1 | name: deb-builder 2 | 3 | # Controls when the workflow will run 4 | on: 5 | release: 6 | types: 7 | - created 8 | # Allows you to run this workflow manually from the Actions tab 9 | workflow_dispatch: 10 | 11 | # A workflow run is made up of one or more jobs that can run sequentially or in parallel 12 | jobs: 13 | # This workflow contains a single job called "build" 14 | create-update-deb: 15 | # The type of runner that the job will run on 16 | runs-on: ubuntu-latest 17 | 18 | # Steps represent a sequence of tasks that will be executed as part of the job 19 | steps: 20 | 21 | - name: save working directory in variable 'DIR' 22 | run: echo "DIR=$(pwd)" >> $GITHUB_ENV 23 | 24 | - name: Clone repo 25 | run: git clone https://github.com/Crilum/update 26 | # Runs a single command using the runners shell 27 | - name: Prepare for building 28 | run: | 29 | LATEST=`curl -s https://api.github.com/repos/Crilum/update/releases/latest | grep -oP '"tag_name": "\K(.*)(?=")' | tr -d 'v'` 30 | cd update 31 | mkdir updatedeb && cd updatedeb 32 | mkdir -p usr/bin/ 33 | mv ../update usr/bin/update 34 | mkdir DEBIAN 35 | cd DEBIAN 36 | wget -O control https://github.com/Crilum/update/raw/main/debian/control 37 | echo "Version: ${LATEST}" >> control 38 | wget -O postinst https://github.com/Crilum/update/raw/main/debian/postinst 39 | chmod 775 postinst 40 | cd .. 41 | cd .. 42 | dpkg-deb --build updatedeb update_${LATEST}_all.deb 43 | echo "DEB=$(basename update*.deb)" >> $GITHUB_ENV 44 | 45 | - name: Upload to release 46 | uses: docker://gacts/upload-to-release:latest 47 | env: 48 | GITHUB_TOKEN: ${{ secrets.GITHUB_TOKEN }} 49 | with: 50 | file: '${{ env.DIR }}/update/${{ env.DEB }}' 51 | type: 'application/x-debian-package' 52 | -------------------------------------------------------------------------------- /.github/workflows/update2deb.yml: -------------------------------------------------------------------------------- 1 | name: update2deb 2 | 3 | # Controls when the workflow will run 4 | on: 5 | release: 6 | types: 7 | - created 8 | # Allows you to run this workflow manually from the Actions tab 9 | workflow_dispatch: 10 | 11 | # A workflow run is made up of one or more jobs that can run sequentially or in parallel 12 | jobs: 13 | 14 | create-update-deb: 15 | # The type of runner that the job will run on 16 | runs-on: ubuntu-latest 17 | 18 | # Steps represent a sequence of tasks that will be executed as part of the job 19 | steps: 20 | 21 | - name: save working directory in variable 'DIR' 22 | run: echo "DIR=$(pwd)" >> $GITHUB_ENV 23 | 24 | - name: Clone repo 25 | run: git clone https://github.com/Crilum/update 26 | # Runs a single command using the runners shell 27 | - name: Build DEB and RPM 28 | run: | 29 | LATEST=`curl -s https://api.github.com/repos/Crilum/update/releases/latest | grep -oP '"tag_name": "\K(.*)(?=")' | tr -d 'v'` 30 | cd update 31 | mkdir updatedeb && cd updatedeb 32 | mkdir -p usr/bin/ 33 | mv ../update usr/bin/update 34 | mkdir DEBIAN 35 | cd DEBIAN 36 | wget -O control https://github.com/Crilum/update/raw/main/debian/control 37 | echo "Version: ${LATEST}" >> control 38 | wget -O postinst https://github.com/Crilum/update/raw/main/debian/postinst 39 | chmod 775 postinst 40 | cd .. 41 | cd .. 42 | dpkg-deb --build updatedeb update_${LATEST}_all.deb 43 | echo "DEB=$(basename update*.deb)" >> $GITHUB_ENV 44 | 45 | - name: Upload DEB to release 46 | uses: docker://gacts/upload-to-release:latest 47 | env: 48 | GITHUB_TOKEN: ${{ secrets.GITHUB_TOKEN }} 49 | with: 50 | file: '${{ env.DIR }}/update/${{ env.DEB }}' 51 | type: 'application/x-debian-package' 52 | 53 | create-update-rpm: 54 | # The type of runner that the job will run on 55 | runs-on: ubuntu-latest 56 | 57 | # Steps represent a sequence of tasks that will be executed as part of the job 58 | steps: 59 | 60 | - name: save working directory in variable 'DIR' 61 | run: | 62 | echo "DIR=$(pwd)" >> $GITHUB_ENV 63 | echo "VER=$(curl -s https://api.github.com/repos/Crilum/update/releases/latest | grep -oP '\"tag_name\": \"\K(.*)(?=\")' | tr -d 'v')" >> $GITHUB_ENV 64 | 65 | - name: Clone repo 66 | run: git clone https://github.com/Crilum/update 67 | 68 | - name: Build RPM 69 | run: | 70 | cd update 71 | ./rpm/build.sh 72 | cp "$HOME"/rpmbuild/RPMS/noarch/*.rpm . 73 | echo "RPM=$(basename update*.rpm)" >> $GITHUB_ENV 74 | - name: Upload RPM to release 75 | uses: docker://gacts/upload-to-release:latest 76 | env: 77 | GITHUB_TOKEN: ${{ secrets.GITHUB_TOKEN }} 78 | with: 79 | file: '${{ env.DIR }}/update/${{ env.RPM }}' 80 | type: 'application/x-rpm' 81 | 82 | -------------------------------------------------------------------------------- /CODE_OF_CONDUCT.md: -------------------------------------------------------------------------------- 1 | # Contributor Covenant Code of Conduct 2 | 3 | ## Our Pledge 4 | 5 | We as members, contributors, and leaders pledge to make participation in our 6 | community a harassment-free experience for everyone, regardless of age, body 7 | size, visible or invisible disability, ethnicity, sex characteristics, gender 8 | identity and expression, level of experience, education, socio-economic status, 9 | nationality, personal appearance, race, religion, or sexual identity 10 | and orientation. 11 | 12 | We pledge to act and interact in ways that contribute to an open, welcoming, 13 | diverse, inclusive, and healthy community. 14 | 15 | ## Our Standards 16 | 17 | Examples of behavior that contributes to a positive environment for our 18 | community include: 19 | 20 | * Demonstrating empathy and kindness toward other people 21 | * Being respectful of differing opinions, viewpoints, and experiences 22 | * Giving and gracefully accepting constructive feedback 23 | * Accepting responsibility and apologizing to those affected by our mistakes, 24 | and learning from the experience 25 | * Focusing on what is best not just for us as individuals, but for the 26 | overall community 27 | 28 | Examples of unacceptable behavior include: 29 | 30 | * The use of sexualized language or imagery, and sexual attention or 31 | advances of any kind 32 | * Trolling, insulting or derogatory comments, and personal or political attacks 33 | * Public or private harassment 34 | * Publishing others' private information, such as a physical or email 35 | address, without their explicit permission 36 | * Other conduct which could reasonably be considered inappropriate in a 37 | professional setting 38 | 39 | ## Enforcement Responsibilities 40 | 41 | Community leaders are responsible for clarifying and enforcing our standards of 42 | acceptable behavior and will take appropriate and fair corrective action in 43 | response to any behavior that they deem inappropriate, threatening, offensive, 44 | or harmful. 45 | 46 | Community leaders have the right and responsibility to remove, edit, or reject 47 | comments, commits, code, wiki edits, issues, and other contributions that are 48 | not aligned to this Code of Conduct, and will communicate reasons for moderation 49 | decisions when appropriate. 50 | 51 | ## Scope 52 | 53 | This Code of Conduct applies within all community spaces, and also applies when 54 | an individual is officially representing the community in public spaces. 55 | Examples of representing our community include using an official e-mail address, 56 | posting via an official social media account, or acting as an appointed 57 | representative at an online or offline event. 58 | 59 | ## Enforcement 60 | 61 | Instances of abusive, harassing, or otherwise unacceptable behavior may be 62 | reported to the community leaders responsible for enforcement at 63 | . 64 | All complaints will be reviewed and investigated promptly and fairly. 65 | 66 | All community leaders are obligated to respect the privacy and security of the 67 | reporter of any incident. 68 | 69 | ## Enforcement Guidelines 70 | 71 | Community leaders will follow these Community Impact Guidelines in determining 72 | the consequences for any action they deem in violation of this Code of Conduct: 73 | 74 | ### 1. Correction 75 | 76 | **Community Impact**: Use of inappropriate language or other behavior deemed 77 | unprofessional or unwelcome in the community. 78 | 79 | **Consequence**: A private, written warning from community leaders, providing 80 | clarity around the nature of the violation and an explanation of why the 81 | behavior was inappropriate. A public apology may be requested. 82 | 83 | ### 2. Warning 84 | 85 | **Community Impact**: A violation through a single incident or series 86 | of actions. 87 | 88 | **Consequence**: A warning with consequences for continued behavior. No 89 | interaction with the people involved, including unsolicited interaction with 90 | those enforcing the Code of Conduct, for a specified period of time. This 91 | includes avoiding interactions in community spaces as well as external channels 92 | like social media. Violating these terms may lead to a temporary or 93 | permanent ban. 94 | 95 | ### 3. Temporary Ban 96 | 97 | **Community Impact**: A serious violation of community standards, including 98 | sustained inappropriate behavior. 99 | 100 | **Consequence**: A temporary ban from any sort of interaction or public 101 | communication with the community for a specified period of time. No public or 102 | private interaction with the people involved, including unsolicited interaction 103 | with those enforcing the Code of Conduct, is allowed during this period. 104 | Violating these terms may lead to a permanent ban. 105 | 106 | ### 4. Permanent Ban 107 | 108 | **Community Impact**: Demonstrating a pattern of violation of community 109 | standards, including sustained inappropriate behavior, harassment of an 110 | individual, or aggression toward or disparagement of classes of individuals. 111 | 112 | **Consequence**: A permanent ban from any sort of public interaction within 113 | the community. 114 | 115 | ## Attribution 116 | 117 | This Code of Conduct is adapted from the [Contributor Covenant][homepage], 118 | version 2.0, available at 119 | https://www.contributor-covenant.org/version/2/0/code_of_conduct.html. 120 | 121 | Community Impact Guidelines were inspired by [Mozilla's code of conduct 122 | enforcement ladder](https://github.com/mozilla/diversity). 123 | 124 | [homepage]: https://www.contributor-covenant.org 125 | 126 | For answers to common questions about this code of conduct, see the FAQ at 127 | https://www.contributor-covenant.org/faq. Translations are available at 128 | https://www.contributor-covenant.org/translations. 129 | -------------------------------------------------------------------------------- /LICENSE: -------------------------------------------------------------------------------- 1 | GNU GENERAL PUBLIC LICENSE 2 | Version 3, 29 June 2007 3 | 4 | Copyright (C) 2007 Free Software Foundation, Inc. 5 | Everyone is permitted to copy and distribute verbatim copies 6 | of this license document, but changing it is not allowed. 7 | 8 | Preamble 9 | 10 | The GNU General Public License is a free, copyleft license for 11 | software and other kinds of works. 12 | 13 | The licenses for most software and other practical works are designed 14 | to take away your freedom to share and change the works. By contrast, 15 | the GNU General Public License is intended to guarantee your freedom to 16 | share and change all versions of a program--to make sure it remains free 17 | software for all its users. We, the Free Software Foundation, use the 18 | GNU General Public License for most of our software; it applies also to 19 | any other work released this way by its authors. You can apply it to 20 | your programs, too. 21 | 22 | When we speak of free software, we are referring to freedom, not 23 | price. Our General Public Licenses are designed to make sure that you 24 | have the freedom to distribute copies of free software (and charge for 25 | them if you wish), that you receive source code or can get it if you 26 | want it, that you can change the software or use pieces of it in new 27 | free programs, and that you know you can do these things. 28 | 29 | To protect your rights, we need to prevent others from denying you 30 | these rights or asking you to surrender the rights. Therefore, you have 31 | certain responsibilities if you distribute copies of the software, or if 32 | you modify it: responsibilities to respect the freedom of others. 33 | 34 | For example, if you distribute copies of such a program, whether 35 | gratis or for a fee, you must pass on to the recipients the same 36 | freedoms that you received. You must make sure that they, too, receive 37 | or can get the source code. And you must show them these terms so they 38 | know their rights. 39 | 40 | Developers that use the GNU GPL protect your rights with two steps: 41 | (1) assert copyright on the software, and (2) offer you this License 42 | giving you legal permission to copy, distribute and/or modify it. 43 | 44 | For the developers' and authors' protection, the GPL clearly explains 45 | that there is no warranty for this free software. For both users' and 46 | authors' sake, the GPL requires that modified versions be marked as 47 | changed, so that their problems will not be attributed erroneously to 48 | authors of previous versions. 49 | 50 | Some devices are designed to deny users access to install or run 51 | modified versions of the software inside them, although the manufacturer 52 | can do so. This is fundamentally incompatible with the aim of 53 | protecting users' freedom to change the software. The systematic 54 | pattern of such abuse occurs in the area of products for individuals to 55 | use, which is precisely where it is most unacceptable. Therefore, we 56 | have designed this version of the GPL to prohibit the practice for those 57 | products. If such problems arise substantially in other domains, we 58 | stand ready to extend this provision to those domains in future versions 59 | of the GPL, as needed to protect the freedom of users. 60 | 61 | Finally, every program is threatened constantly by software patents. 62 | States should not allow patents to restrict development and use of 63 | software on general-purpose computers, but in those that do, we wish to 64 | avoid the special danger that patents applied to a free program could 65 | make it effectively proprietary. To prevent this, the GPL assures that 66 | patents cannot be used to render the program non-free. 67 | 68 | The precise terms and conditions for copying, distribution and 69 | modification follow. 70 | 71 | TERMS AND CONDITIONS 72 | 73 | 0. Definitions. 74 | 75 | "This License" refers to version 3 of the GNU General Public License. 76 | 77 | "Copyright" also means copyright-like laws that apply to other kinds of 78 | works, such as semiconductor masks. 79 | 80 | "The Program" refers to any copyrightable work licensed under this 81 | License. Each licensee is addressed as "you". "Licensees" and 82 | "recipients" may be individuals or organizations. 83 | 84 | To "modify" a work means to copy from or adapt all or part of the work 85 | in a fashion requiring copyright permission, other than the making of an 86 | exact copy. The resulting work is called a "modified version" of the 87 | earlier work or a work "based on" the earlier work. 88 | 89 | A "covered work" means either the unmodified Program or a work based 90 | on the Program. 91 | 92 | To "propagate" a work means to do anything with it that, without 93 | permission, would make you directly or secondarily liable for 94 | infringement under applicable copyright law, except executing it on a 95 | computer or modifying a private copy. Propagation includes copying, 96 | distribution (with or without modification), making available to the 97 | public, and in some countries other activities as well. 98 | 99 | To "convey" a work means any kind of propagation that enables other 100 | parties to make or receive copies. Mere interaction with a user through 101 | a computer network, with no transfer of a copy, is not conveying. 102 | 103 | An interactive user interface displays "Appropriate Legal Notices" 104 | to the extent that it includes a convenient and prominently visible 105 | feature that (1) displays an appropriate copyright notice, and (2) 106 | tells the user that there is no warranty for the work (except to the 107 | extent that warranties are provided), that licensees may convey the 108 | work under this License, and how to view a copy of this License. If 109 | the interface presents a list of user commands or options, such as a 110 | menu, a prominent item in the list meets this criterion. 111 | 112 | 1. Source Code. 113 | 114 | The "source code" for a work means the preferred form of the work 115 | for making modifications to it. "Object code" means any non-source 116 | form of a work. 117 | 118 | A "Standard Interface" means an interface that either is an official 119 | standard defined by a recognized standards body, or, in the case of 120 | interfaces specified for a particular programming language, one that 121 | is widely used among developers working in that language. 122 | 123 | The "System Libraries" of an executable work include anything, other 124 | than the work as a whole, that (a) is included in the normal form of 125 | packaging a Major Component, but which is not part of that Major 126 | Component, and (b) serves only to enable use of the work with that 127 | Major Component, or to implement a Standard Interface for which an 128 | implementation is available to the public in source code form. A 129 | "Major Component", in this context, means a major essential component 130 | (kernel, window system, and so on) of the specific operating system 131 | (if any) on which the executable work runs, or a compiler used to 132 | produce the work, or an object code interpreter used to run it. 133 | 134 | The "Corresponding Source" for a work in object code form means all 135 | the source code needed to generate, install, and (for an executable 136 | work) run the object code and to modify the work, including scripts to 137 | control those activities. However, it does not include the work's 138 | System Libraries, or general-purpose tools or generally available free 139 | programs which are used unmodified in performing those activities but 140 | which are not part of the work. For example, Corresponding Source 141 | includes interface definition files associated with source files for 142 | the work, and the source code for shared libraries and dynamically 143 | linked subprograms that the work is specifically designed to require, 144 | such as by intimate data communication or control flow between those 145 | subprograms and other parts of the work. 146 | 147 | The Corresponding Source need not include anything that users 148 | can regenerate automatically from other parts of the Corresponding 149 | Source. 150 | 151 | The Corresponding Source for a work in source code form is that 152 | same work. 153 | 154 | 2. Basic Permissions. 155 | 156 | All rights granted under this License are granted for the term of 157 | copyright on the Program, and are irrevocable provided the stated 158 | conditions are met. This License explicitly affirms your unlimited 159 | permission to run the unmodified Program. The output from running a 160 | covered work is covered by this License only if the output, given its 161 | content, constitutes a covered work. This License acknowledges your 162 | rights of fair use or other equivalent, as provided by copyright law. 163 | 164 | You may make, run and propagate covered works that you do not 165 | convey, without conditions so long as your license otherwise remains 166 | in force. You may convey covered works to others for the sole purpose 167 | of having them make modifications exclusively for you, or provide you 168 | with facilities for running those works, provided that you comply with 169 | the terms of this License in conveying all material for which you do 170 | not control copyright. Those thus making or running the covered works 171 | for you must do so exclusively on your behalf, under your direction 172 | and control, on terms that prohibit them from making any copies of 173 | your copyrighted material outside their relationship with you. 174 | 175 | Conveying under any other circumstances is permitted solely under 176 | the conditions stated below. Sublicensing is not allowed; section 10 177 | makes it unnecessary. 178 | 179 | 3. Protecting Users' Legal Rights From Anti-Circumvention Law. 180 | 181 | No covered work shall be deemed part of an effective technological 182 | measure under any applicable law fulfilling obligations under article 183 | 11 of the WIPO copyright treaty adopted on 20 December 1996, or 184 | similar laws prohibiting or restricting circumvention of such 185 | measures. 186 | 187 | When you convey a covered work, you waive any legal power to forbid 188 | circumvention of technological measures to the extent such circumvention 189 | is effected by exercising rights under this License with respect to 190 | the covered work, and you disclaim any intention to limit operation or 191 | modification of the work as a means of enforcing, against the work's 192 | users, your or third parties' legal rights to forbid circumvention of 193 | technological measures. 194 | 195 | 4. Conveying Verbatim Copies. 196 | 197 | You may convey verbatim copies of the Program's source code as you 198 | receive it, in any medium, provided that you conspicuously and 199 | appropriately publish on each copy an appropriate copyright notice; 200 | keep intact all notices stating that this License and any 201 | non-permissive terms added in accord with section 7 apply to the code; 202 | keep intact all notices of the absence of any warranty; and give all 203 | recipients a copy of this License along with the Program. 204 | 205 | You may charge any price or no price for each copy that you convey, 206 | and you may offer support or warranty protection for a fee. 207 | 208 | 5. Conveying Modified Source Versions. 209 | 210 | You may convey a work based on the Program, or the modifications to 211 | produce it from the Program, in the form of source code under the 212 | terms of section 4, provided that you also meet all of these conditions: 213 | 214 | a) The work must carry prominent notices stating that you modified 215 | it, and giving a relevant date. 216 | 217 | b) The work must carry prominent notices stating that it is 218 | released under this License and any conditions added under section 219 | 7. This requirement modifies the requirement in section 4 to 220 | "keep intact all notices". 221 | 222 | c) You must license the entire work, as a whole, under this 223 | License to anyone who comes into possession of a copy. This 224 | License will therefore apply, along with any applicable section 7 225 | additional terms, to the whole of the work, and all its parts, 226 | regardless of how they are packaged. This License gives no 227 | permission to license the work in any other way, but it does not 228 | invalidate such permission if you have separately received it. 229 | 230 | d) If the work has interactive user interfaces, each must display 231 | Appropriate Legal Notices; however, if the Program has interactive 232 | interfaces that do not display Appropriate Legal Notices, your 233 | work need not make them do so. 234 | 235 | A compilation of a covered work with other separate and independent 236 | works, which are not by their nature extensions of the covered work, 237 | and which are not combined with it such as to form a larger program, 238 | in or on a volume of a storage or distribution medium, is called an 239 | "aggregate" if the compilation and its resulting copyright are not 240 | used to limit the access or legal rights of the compilation's users 241 | beyond what the individual works permit. Inclusion of a covered work 242 | in an aggregate does not cause this License to apply to the other 243 | parts of the aggregate. 244 | 245 | 6. Conveying Non-Source Forms. 246 | 247 | You may convey a covered work in object code form under the terms 248 | of sections 4 and 5, provided that you also convey the 249 | machine-readable Corresponding Source under the terms of this License, 250 | in one of these ways: 251 | 252 | a) Convey the object code in, or embodied in, a physical product 253 | (including a physical distribution medium), accompanied by the 254 | Corresponding Source fixed on a durable physical medium 255 | customarily used for software interchange. 256 | 257 | b) Convey the object code in, or embodied in, a physical product 258 | (including a physical distribution medium), accompanied by a 259 | written offer, valid for at least three years and valid for as 260 | long as you offer spare parts or customer support for that product 261 | model, to give anyone who possesses the object code either (1) a 262 | copy of the Corresponding Source for all the software in the 263 | product that is covered by this License, on a durable physical 264 | medium customarily used for software interchange, for a price no 265 | more than your reasonable cost of physically performing this 266 | conveying of source, or (2) access to copy the 267 | Corresponding Source from a network server at no charge. 268 | 269 | c) Convey individual copies of the object code with a copy of the 270 | written offer to provide the Corresponding Source. This 271 | alternative is allowed only occasionally and noncommercially, and 272 | only if you received the object code with such an offer, in accord 273 | with subsection 6b. 274 | 275 | d) Convey the object code by offering access from a designated 276 | place (gratis or for a charge), and offer equivalent access to the 277 | Corresponding Source in the same way through the same place at no 278 | further charge. You need not require recipients to copy the 279 | Corresponding Source along with the object code. If the place to 280 | copy the object code is a network server, the Corresponding Source 281 | may be on a different server (operated by you or a third party) 282 | that supports equivalent copying facilities, provided you maintain 283 | clear directions next to the object code saying where to find the 284 | Corresponding Source. Regardless of what server hosts the 285 | Corresponding Source, you remain obligated to ensure that it is 286 | available for as long as needed to satisfy these requirements. 287 | 288 | e) Convey the object code using peer-to-peer transmission, provided 289 | you inform other peers where the object code and Corresponding 290 | Source of the work are being offered to the general public at no 291 | charge under subsection 6d. 292 | 293 | A separable portion of the object code, whose source code is excluded 294 | from the Corresponding Source as a System Library, need not be 295 | included in conveying the object code work. 296 | 297 | A "User Product" is either (1) a "consumer product", which means any 298 | tangible personal property which is normally used for personal, family, 299 | or household purposes, or (2) anything designed or sold for incorporation 300 | into a dwelling. In determining whether a product is a consumer product, 301 | doubtful cases shall be resolved in favor of coverage. For a particular 302 | product received by a particular user, "normally used" refers to a 303 | typical or common use of that class of product, regardless of the status 304 | of the particular user or of the way in which the particular user 305 | actually uses, or expects or is expected to use, the product. A product 306 | is a consumer product regardless of whether the product has substantial 307 | commercial, industrial or non-consumer uses, unless such uses represent 308 | the only significant mode of use of the product. 309 | 310 | "Installation Information" for a User Product means any methods, 311 | procedures, authorization keys, or other information required to install 312 | and execute modified versions of a covered work in that User Product from 313 | a modified version of its Corresponding Source. The information must 314 | suffice to ensure that the continued functioning of the modified object 315 | code is in no case prevented or interfered with solely because 316 | modification has been made. 317 | 318 | If you convey an object code work under this section in, or with, or 319 | specifically for use in, a User Product, and the conveying occurs as 320 | part of a transaction in which the right of possession and use of the 321 | User Product is transferred to the recipient in perpetuity or for a 322 | fixed term (regardless of how the transaction is characterized), the 323 | Corresponding Source conveyed under this section must be accompanied 324 | by the Installation Information. But this requirement does not apply 325 | if neither you nor any third party retains the ability to install 326 | modified object code on the User Product (for example, the work has 327 | been installed in ROM). 328 | 329 | The requirement to provide Installation Information does not include a 330 | requirement to continue to provide support service, warranty, or updates 331 | for a work that has been modified or installed by the recipient, or for 332 | the User Product in which it has been modified or installed. Access to a 333 | network may be denied when the modification itself materially and 334 | adversely affects the operation of the network or violates the rules and 335 | protocols for communication across the network. 336 | 337 | Corresponding Source conveyed, and Installation Information provided, 338 | in accord with this section must be in a format that is publicly 339 | documented (and with an implementation available to the public in 340 | source code form), and must require no special password or key for 341 | unpacking, reading or copying. 342 | 343 | 7. Additional Terms. 344 | 345 | "Additional permissions" are terms that supplement the terms of this 346 | License by making exceptions from one or more of its conditions. 347 | Additional permissions that are applicable to the entire Program shall 348 | be treated as though they were included in this License, to the extent 349 | that they are valid under applicable law. If additional permissions 350 | apply only to part of the Program, that part may be used separately 351 | under those permissions, but the entire Program remains governed by 352 | this License without regard to the additional permissions. 353 | 354 | When you convey a copy of a covered work, you may at your option 355 | remove any additional permissions from that copy, or from any part of 356 | it. (Additional permissions may be written to require their own 357 | removal in certain cases when you modify the work.) You may place 358 | additional permissions on material, added by you to a covered work, 359 | for which you have or can give appropriate copyright permission. 360 | 361 | Notwithstanding any other provision of this License, for material you 362 | add to a covered work, you may (if authorized by the copyright holders of 363 | that material) supplement the terms of this License with terms: 364 | 365 | a) Disclaiming warranty or limiting liability differently from the 366 | terms of sections 15 and 16 of this License; or 367 | 368 | b) Requiring preservation of specified reasonable legal notices or 369 | author attributions in that material or in the Appropriate Legal 370 | Notices displayed by works containing it; or 371 | 372 | c) Prohibiting misrepresentation of the origin of that material, or 373 | requiring that modified versions of such material be marked in 374 | reasonable ways as different from the original version; or 375 | 376 | d) Limiting the use for publicity purposes of names of licensors or 377 | authors of the material; or 378 | 379 | e) Declining to grant rights under trademark law for use of some 380 | trade names, trademarks, or service marks; or 381 | 382 | f) Requiring indemnification of licensors and authors of that 383 | material by anyone who conveys the material (or modified versions of 384 | it) with contractual assumptions of liability to the recipient, for 385 | any liability that these contractual assumptions directly impose on 386 | those licensors and authors. 387 | 388 | All other non-permissive additional terms are considered "further 389 | restrictions" within the meaning of section 10. If the Program as you 390 | received it, or any part of it, contains a notice stating that it is 391 | governed by this License along with a term that is a further 392 | restriction, you may remove that term. If a license document contains 393 | a further restriction but permits relicensing or conveying under this 394 | License, you may add to a covered work material governed by the terms 395 | of that license document, provided that the further restriction does 396 | not survive such relicensing or conveying. 397 | 398 | If you add terms to a covered work in accord with this section, you 399 | must place, in the relevant source files, a statement of the 400 | additional terms that apply to those files, or a notice indicating 401 | where to find the applicable terms. 402 | 403 | Additional terms, permissive or non-permissive, may be stated in the 404 | form of a separately written license, or stated as exceptions; 405 | the above requirements apply either way. 406 | 407 | 8. Termination. 408 | 409 | You may not propagate or modify a covered work except as expressly 410 | provided under this License. Any attempt otherwise to propagate or 411 | modify it is void, and will automatically terminate your rights under 412 | this License (including any patent licenses granted under the third 413 | paragraph of section 11). 414 | 415 | However, if you cease all violation of this License, then your 416 | license from a particular copyright holder is reinstated (a) 417 | provisionally, unless and until the copyright holder explicitly and 418 | finally terminates your license, and (b) permanently, if the copyright 419 | holder fails to notify you of the violation by some reasonable means 420 | prior to 60 days after the cessation. 421 | 422 | Moreover, your license from a particular copyright holder is 423 | reinstated permanently if the copyright holder notifies you of the 424 | violation by some reasonable means, this is the first time you have 425 | received notice of violation of this License (for any work) from that 426 | copyright holder, and you cure the violation prior to 30 days after 427 | your receipt of the notice. 428 | 429 | Termination of your rights under this section does not terminate the 430 | licenses of parties who have received copies or rights from you under 431 | this License. If your rights have been terminated and not permanently 432 | reinstated, you do not qualify to receive new licenses for the same 433 | material under section 10. 434 | 435 | 9. Acceptance Not Required for Having Copies. 436 | 437 | You are not required to accept this License in order to receive or 438 | run a copy of the Program. Ancillary propagation of a covered work 439 | occurring solely as a consequence of using peer-to-peer transmission 440 | to receive a copy likewise does not require acceptance. However, 441 | nothing other than this License grants you permission to propagate or 442 | modify any covered work. These actions infringe copyright if you do 443 | not accept this License. Therefore, by modifying or propagating a 444 | covered work, you indicate your acceptance of this License to do so. 445 | 446 | 10. Automatic Licensing of Downstream Recipients. 447 | 448 | Each time you convey a covered work, the recipient automatically 449 | receives a license from the original licensors, to run, modify and 450 | propagate that work, subject to this License. You are not responsible 451 | for enforcing compliance by third parties with this License. 452 | 453 | An "entity transaction" is a transaction transferring control of an 454 | organization, or substantially all assets of one, or subdividing an 455 | organization, or merging organizations. If propagation of a covered 456 | work results from an entity transaction, each party to that 457 | transaction who receives a copy of the work also receives whatever 458 | licenses to the work the party's predecessor in interest had or could 459 | give under the previous paragraph, plus a right to possession of the 460 | Corresponding Source of the work from the predecessor in interest, if 461 | the predecessor has it or can get it with reasonable efforts. 462 | 463 | You may not impose any further restrictions on the exercise of the 464 | rights granted or affirmed under this License. For example, you may 465 | not impose a license fee, royalty, or other charge for exercise of 466 | rights granted under this License, and you may not initiate litigation 467 | (including a cross-claim or counterclaim in a lawsuit) alleging that 468 | any patent claim is infringed by making, using, selling, offering for 469 | sale, or importing the Program or any portion of it. 470 | 471 | 11. Patents. 472 | 473 | A "contributor" is a copyright holder who authorizes use under this 474 | License of the Program or a work on which the Program is based. The 475 | work thus licensed is called the contributor's "contributor version". 476 | 477 | A contributor's "essential patent claims" are all patent claims 478 | owned or controlled by the contributor, whether already acquired or 479 | hereafter acquired, that would be infringed by some manner, permitted 480 | by this License, of making, using, or selling its contributor version, 481 | but do not include claims that would be infringed only as a 482 | consequence of further modification of the contributor version. For 483 | purposes of this definition, "control" includes the right to grant 484 | patent sublicenses in a manner consistent with the requirements of 485 | this License. 486 | 487 | Each contributor grants you a non-exclusive, worldwide, royalty-free 488 | patent license under the contributor's essential patent claims, to 489 | make, use, sell, offer for sale, import and otherwise run, modify and 490 | propagate the contents of its contributor version. 491 | 492 | In the following three paragraphs, a "patent license" is any express 493 | agreement or commitment, however denominated, not to enforce a patent 494 | (such as an express permission to practice a patent or covenant not to 495 | sue for patent infringement). To "grant" such a patent license to a 496 | party means to make such an agreement or commitment not to enforce a 497 | patent against the party. 498 | 499 | If you convey a covered work, knowingly relying on a patent license, 500 | and the Corresponding Source of the work is not available for anyone 501 | to copy, free of charge and under the terms of this License, through a 502 | publicly available network server or other readily accessible means, 503 | then you must either (1) cause the Corresponding Source to be so 504 | available, or (2) arrange to deprive yourself of the benefit of the 505 | patent license for this particular work, or (3) arrange, in a manner 506 | consistent with the requirements of this License, to extend the patent 507 | license to downstream recipients. "Knowingly relying" means you have 508 | actual knowledge that, but for the patent license, your conveying the 509 | covered work in a country, or your recipient's use of the covered work 510 | in a country, would infringe one or more identifiable patents in that 511 | country that you have reason to believe are valid. 512 | 513 | If, pursuant to or in connection with a single transaction or 514 | arrangement, you convey, or propagate by procuring conveyance of, a 515 | covered work, and grant a patent license to some of the parties 516 | receiving the covered work authorizing them to use, propagate, modify 517 | or convey a specific copy of the covered work, then the patent license 518 | you grant is automatically extended to all recipients of the covered 519 | work and works based on it. 520 | 521 | A patent license is "discriminatory" if it does not include within 522 | the scope of its coverage, prohibits the exercise of, or is 523 | conditioned on the non-exercise of one or more of the rights that are 524 | specifically granted under this License. You may not convey a covered 525 | work if you are a party to an arrangement with a third party that is 526 | in the business of distributing software, under which you make payment 527 | to the third party based on the extent of your activity of conveying 528 | the work, and under which the third party grants, to any of the 529 | parties who would receive the covered work from you, a discriminatory 530 | patent license (a) in connection with copies of the covered work 531 | conveyed by you (or copies made from those copies), or (b) primarily 532 | for and in connection with specific products or compilations that 533 | contain the covered work, unless you entered into that arrangement, 534 | or that patent license was granted, prior to 28 March 2007. 535 | 536 | Nothing in this License shall be construed as excluding or limiting 537 | any implied license or other defenses to infringement that may 538 | otherwise be available to you under applicable patent law. 539 | 540 | 12. No Surrender of Others' Freedom. 541 | 542 | If conditions are imposed on you (whether by court order, agreement or 543 | otherwise) that contradict the conditions of this License, they do not 544 | excuse you from the conditions of this License. If you cannot convey a 545 | covered work so as to satisfy simultaneously your obligations under this 546 | License and any other pertinent obligations, then as a consequence you may 547 | not convey it at all. For example, if you agree to terms that obligate you 548 | to collect a royalty for further conveying from those to whom you convey 549 | the Program, the only way you could satisfy both those terms and this 550 | License would be to refrain entirely from conveying the Program. 551 | 552 | 13. Use with the GNU Affero General Public License. 553 | 554 | Notwithstanding any other provision of this License, you have 555 | permission to link or combine any covered work with a work licensed 556 | under version 3 of the GNU Affero General Public License into a single 557 | combined work, and to convey the resulting work. The terms of this 558 | License will continue to apply to the part which is the covered work, 559 | but the special requirements of the GNU Affero General Public License, 560 | section 13, concerning interaction through a network will apply to the 561 | combination as such. 562 | 563 | 14. Revised Versions of this License. 564 | 565 | The Free Software Foundation may publish revised and/or new versions of 566 | the GNU General Public License from time to time. Such new versions will 567 | be similar in spirit to the present version, but may differ in detail to 568 | address new problems or concerns. 569 | 570 | Each version is given a distinguishing version number. If the 571 | Program specifies that a certain numbered version of the GNU General 572 | Public License "or any later version" applies to it, you have the 573 | option of following the terms and conditions either of that numbered 574 | version or of any later version published by the Free Software 575 | Foundation. If the Program does not specify a version number of the 576 | GNU General Public License, you may choose any version ever published 577 | by the Free Software Foundation. 578 | 579 | If the Program specifies that a proxy can decide which future 580 | versions of the GNU General Public License can be used, that proxy's 581 | public statement of acceptance of a version permanently authorizes you 582 | to choose that version for the Program. 583 | 584 | Later license versions may give you additional or different 585 | permissions. However, no additional obligations are imposed on any 586 | author or copyright holder as a result of your choosing to follow a 587 | later version. 588 | 589 | 15. Disclaimer of Warranty. 590 | 591 | THERE IS NO WARRANTY FOR THE PROGRAM, TO THE EXTENT PERMITTED BY 592 | APPLICABLE LAW. EXCEPT WHEN OTHERWISE STATED IN WRITING THE COPYRIGHT 593 | HOLDERS AND/OR OTHER PARTIES PROVIDE THE PROGRAM "AS IS" WITHOUT WARRANTY 594 | OF ANY KIND, EITHER EXPRESSED OR IMPLIED, INCLUDING, BUT NOT LIMITED TO, 595 | THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR 596 | PURPOSE. THE ENTIRE RISK AS TO THE QUALITY AND PERFORMANCE OF THE PROGRAM 597 | IS WITH YOU. SHOULD THE PROGRAM PROVE DEFECTIVE, YOU ASSUME THE COST OF 598 | ALL NECESSARY SERVICING, REPAIR OR CORRECTION. 599 | 600 | 16. Limitation of Liability. 601 | 602 | IN NO EVENT UNLESS REQUIRED BY APPLICABLE LAW OR AGREED TO IN WRITING 603 | WILL ANY COPYRIGHT HOLDER, OR ANY OTHER PARTY WHO MODIFIES AND/OR CONVEYS 604 | THE PROGRAM AS PERMITTED ABOVE, BE LIABLE TO YOU FOR DAMAGES, INCLUDING ANY 605 | GENERAL, SPECIAL, INCIDENTAL OR CONSEQUENTIAL DAMAGES ARISING OUT OF THE 606 | USE OR INABILITY TO USE THE PROGRAM (INCLUDING BUT NOT LIMITED TO LOSS OF 607 | DATA OR DATA BEING RENDERED INACCURATE OR LOSSES SUSTAINED BY YOU OR THIRD 608 | PARTIES OR A FAILURE OF THE PROGRAM TO OPERATE WITH ANY OTHER PROGRAMS), 609 | EVEN IF SUCH HOLDER OR OTHER PARTY HAS BEEN ADVISED OF THE POSSIBILITY OF 610 | SUCH DAMAGES. 611 | 612 | 17. Interpretation of Sections 15 and 16. 613 | 614 | If the disclaimer of warranty and limitation of liability provided 615 | above cannot be given local legal effect according to their terms, 616 | reviewing courts shall apply local law that most closely approximates 617 | an absolute waiver of all civil liability in connection with the 618 | Program, unless a warranty or assumption of liability accompanies a 619 | copy of the Program in return for a fee. 620 | 621 | END OF TERMS AND CONDITIONS 622 | 623 | How to Apply These Terms to Your New Programs 624 | 625 | If you develop a new program, and you want it to be of the greatest 626 | possible use to the public, the best way to achieve this is to make it 627 | free software which everyone can redistribute and change under these terms. 628 | 629 | To do so, attach the following notices to the program. It is safest 630 | to attach them to the start of each source file to most effectively 631 | state the exclusion of warranty; and each file should have at least 632 | the "copyright" line and a pointer to where the full notice is found. 633 | 634 | 635 | Copyright (C) 636 | 637 | This program is free software: you can redistribute it and/or modify 638 | it under the terms of the GNU General Public License as published by 639 | the Free Software Foundation, either version 3 of the License, or 640 | (at your option) any later version. 641 | 642 | This program is distributed in the hope that it will be useful, 643 | but WITHOUT ANY WARRANTY; without even the implied warranty of 644 | MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the 645 | GNU General Public License for more details. 646 | 647 | You should have received a copy of the GNU General Public License 648 | along with this program. If not, see . 649 | 650 | Also add information on how to contact you by electronic and paper mail. 651 | 652 | If the program does terminal interaction, make it output a short 653 | notice like this when it starts in an interactive mode: 654 | 655 | Copyright (C) 656 | This program comes with ABSOLUTELY NO WARRANTY; for details type `show w'. 657 | This is free software, and you are welcome to redistribute it 658 | under certain conditions; type `show c' for details. 659 | 660 | The hypothetical commands `show w' and `show c' should show the appropriate 661 | parts of the General Public License. Of course, your program's commands 662 | might be different; for a GUI interface, you would use an "about box". 663 | 664 | You should also get your employer (if you work as a programmer) or school, 665 | if any, to sign a "copyright disclaimer" for the program, if necessary. 666 | For more information on this, and how to apply and follow the GNU GPL, see 667 | . 668 | 669 | The GNU General Public License does not permit incorporating your program 670 | into proprietary programs. If your program is a subroutine library, you 671 | may consider it more useful to permit linking proprietary applications with 672 | the library. If this is what you want to do, use the GNU Lesser General 673 | Public License instead of this License. But first, please read 674 | . 675 | -------------------------------------------------------------------------------- /README.md: -------------------------------------------------------------------------------- 1 | ![logo](https://github.com/Crilum/update/blob/main/images/update_simple-100x100.png) 2 | [![update2deb](https://github.com/Crilum/update/actions/workflows/update2deb.yml/badge.svg?branch=main)](https://github.com/Crilum/update/actions/workflows/update2deb.yml) 3 | # update 4 | update is a small script that updates apps from [`Apt`](https://en.wikipedia.org/wiki/APT_(software)), [`Pi-Apps`](https://github.com/Botspot/pi-apps), [`Flatpak`](https://www.flatpak.org/), [`Homebrew`](https://brew.sh), [`NPM`](https://npmjs.com), and the [`Snap Store`](https://snapcraft.io/), a.k.a. [`snapd`](https://snapcraft.io). 5 | 6 | 7 | 8 | 9 | # Install 10 | 11 | ``` 12 | curl -s "https://raw.githubusercontent.com/Crilum/update/main/install" | bash 13 | ``` 14 | 15 | This should work for most systems (Apt-based distros (not Alpine Linux, yet..), DNF-based distros, most other Linux distros, and MacOS). If it doesn't work on your system, [create an issue](https://github.com/Crilum/update/issues/new) (or even better, a PR), and I'll try to help. 16 | 17 |
18 | If you want to install manually | click to expand 19 | 20 |

There are two different ways to download the script, the first one is easier, but you can use the second one if you want.

21 | 22 |

Method 1. Use `wget` and download `update` directly, and copy the script to `/usr/local/bin/`:

23 | 24 | 25 | 1. Make sure `wget` is installed: 26 | 27 | ``` 28 | sudo apt install wget 29 | ``` 30 | 31 | 2. Download the latest version of `update` with `wget`: 32 | 33 | ``` 34 | version="$(curl -s https://api.github.com/repos/Crilum/update/releases/latest | grep -oP '"tag_name": "\K(.*)(?=")')" 35 | wget "https://github.com/Crilum/update/raw/v${version}/update" 36 | ``` 37 | 38 | 3. Move `update` to `/usr/local/bin/`: 39 | 40 | ``` 41 | sudo mv update /usr/local/bin/update 42 | ``` 43 | 44 | 4. Make `update` executable: 45 | 46 | ``` 47 | sudo chmod +x /usr/local/bin/update 48 | ``` 49 | ## 50 | 51 |

Method 2. Use `git clone` and copy the script to `/usr/local/bin/`:

52 | 53 | 1. Clone the latest release of the repository: 54 | 55 | ``` 56 | version="$(curl -s https://api.github.com/repos/Crilum/update/releases/latest | grep -oP '"tag_name": "\K(.*)(?=")')" 57 | git clone https://github.com/Crilum/update/ -b $version 58 | ``` 59 | 60 | 2. Or, if you have GitHub CLI: 61 | 62 | ``` 63 | version="$(curl -s https://api.github.com/repos/Crilum/update/releases/latest | grep -oP '"tag_name": "\K(.*)(?=")')" 64 | gh repo clone Crilum/update -- -b $version 65 | ``` 66 | 67 | 3. Copy the Update Script to `/usr/local/bin/`: 68 | 69 | ``` 70 | cd update && sudo cp update /usr/local/bin/update 71 | ``` 72 | 73 | 4. Make it executable: 74 | 75 | ``` 76 | sudo chmod +x /usr/local/bin/update 77 | ``` 78 | 79 | 5. Remove the cloned repository (This is optional): 80 | 81 | ``` 82 | rm -rf update/ 83 | ``` 84 | 85 |
86 | 87 | # Uninstall 88 | 89 | ### Just uninstall the package: 90 | 91 | #### Apt based distros: 92 | 93 | ``` 94 | sudo apt remove update 95 | ``` 96 | 97 | ### Or, if your system doesn't have an update package: 98 | 99 | #### Other linux: 100 | ``` 101 | sudo rm -f /usr/bin/update /usr/bin/up 102 | ``` 103 | #### MacOS: 104 | 105 | ``` 106 | sudo rm -f /usr/local/bin/update /usr/local/bin/up 107 | ``` 108 | 109 | and you're done! 110 | 111 | 112 | # Usage 113 | You can use `update` like this: 114 | 115 | These are the main options/arguments for update: 116 | ``` 117 | update apt · -a · --apt [packages] Updates apt packages 118 | update all · -A · --all Updates apps on all installed package managers and/or app stores that are supported - Note: This option does not update NPM packages because this can cause trouble. 119 | update pi-apps · -p · --pi-apps Updates Pi-Apps, and apps installed with Pi-Apps 120 | update npm · -n · --npm Updates all npm packages 121 | update snaps · -s · --snaps [snaps] Updates snaps with snapd 122 | update flatpak · -f · --flatpak [packages] Updates flatpak apps 123 | update homebrew · -H · --homebrew Updates Homebrew apps 124 | update pacman · -c · --pacman [packages] Updates pacman apps 125 | update dnf · -d · --dnf Updates dnf packages 126 | update self-update · -u · --self-update Updates the update script 127 | update help · -h · --help Displays this help 128 | update version · -v · --version Prints version 129 | ``` 130 | Flags for update: 131 | ``` 132 | --no-grep-args If this flag is specified, update won't remove arguments that are also packages from the update package list, i.e. 'apt' 133 | ``` 134 | 135 | 136 | ## Todo 137 | - [X] make a unified install script. 138 | - [x] Make a Releases tesing system, so when I release an update GitHub Actions tests installation. 139 | - [ ] Create `Contributing.md`. 140 | - [ ] Create pull request templates. 141 | - [ ] Create a editable configuration for `all` argument 142 | - [ ] Create a more reliable way to check for updates that doesn't depend on a variable in the script, or modify `update2deb` to edit the script and set the right version. 143 | - [ ] Make install uninstall `update` if it's already installed 144 | -------------------------------------------------------------------------------- /debian/control: -------------------------------------------------------------------------------- 1 | Maintainer: Crilum 2 | Summary: Updates apps/packages/dependencies from apt, pi-apps, flatpak, snapd, homebrew, and npm 3 | Name: update 4 | Description: Small script to update apps from package managers 5 | License: gpl-3.0 6 | Architecture: all 7 | Provides: update 8 | Priority: optional 9 | Depends: bash, wget, curl 10 | Section: utils 11 | Package: update 12 | -------------------------------------------------------------------------------- /debian/postinst: -------------------------------------------------------------------------------- 1 | #!/bin/bash 2 | chmod +x /usr/bin/update 3 | if [ ! -e "/usr/bin/up" ]; then 4 | ln -s /usr/bin/update /usr/bin/up 5 | chmod +x /usr/bin/up 6 | else 7 | echo "Warning: The \`up\` command was not created, because the file '/usr/bin/up' already exists. Use \`update\` instead." 8 | fi 9 | exit 0 10 | -------------------------------------------------------------------------------- /debian/postrm: -------------------------------------------------------------------------------- 1 | #!/bin/bash 2 | if [[ -L "/usr/bin/up" ]]; then 3 | rm -rf /usr/bin/up 4 | else 5 | echo "It looks like your '/usr/bin/up' file isn't a symbolic link to '/usr/bin/update', so it hasn't been removed. If you stil want to remove it, you can do so with: sudo rm -f /usr/bin/up" 6 | fi 7 | -------------------------------------------------------------------------------- /images/update_simple-100x100.png: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/Crilum/update/76baf7ee2172d96a27f9a18c391c8581f3bdf26d/images/update_simple-100x100.png -------------------------------------------------------------------------------- /images/update_simple.png: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/Crilum/update/76baf7ee2172d96a27f9a18c391c8581f3bdf26d/images/update_simple.png -------------------------------------------------------------------------------- /install: -------------------------------------------------------------------------------- 1 | #!/bin/bash 2 | 3 | #Color Variables 4 | 5 | NC='\e[0m' 6 | BLACK='\e[0;30m' 7 | RED='\e[0;31m' 8 | GREEN='\e[0;32m' 9 | WHITE='\e[1;37m' 10 | ORANGE='\e[0;33m' 11 | BLUE='\e[0;34m' 12 | PURPLE='\e[0;35m' 13 | CYAN='\e[0;36m' 14 | YELLOW='\e[1;33m' 15 | DARGRAY='\e[1;30m' 16 | 17 | #Lighter Colors 18 | LIGRAY='\e[0;37m' 19 | LIGREEN='\e[1;32m' 20 | LIRED='\e[1;31m' 21 | LIBLUE='\e[1;34m' 22 | LIPURPLE='\e[1;35m' 23 | LICYAN='\e[1;36m' 24 | 25 | #Background Color Variables 26 | 27 | BACKBLACK='\e[0;40m' 28 | BACKRED='\e[0;41m' 29 | BACKGREEN='\e[0;42m' 30 | BACKWHITE='\e[1;47m' 31 | BACKORANGE='\e[0;43m' 32 | BACKBLUE='\e[0;44m' 33 | BACKPURPLE='\e[0;45m' 34 | BACKCYAN='\e[0;46m' 35 | BACKYELLOW='\e[1;43m' 36 | 37 | #Lighter Colors 38 | BACKLIGRAY='\e[0;47m' 39 | BACKLIGREEN='\e[1;42m' 40 | BACKLIRED='\e[1;41m' 41 | BACKLIBLUE='\e[1;44m' 42 | BACKLIPURPLE='\e[1;45m' 43 | BACKLICYAN='\e[1;46m' 44 | 45 | #Markup Variables 46 | UNDERLINE='\e[4m' 47 | BOLD='\e[1m' 48 | BLINK='\e[5m' 49 | REVVID='\e[7m' 50 | 51 | # Code 52 | 53 | if [ "$(whoami)" == "root" ]; then 54 | sudo="" 55 | else 56 | sudo="sudo" 57 | fi 58 | 59 | if [[ ! "$SHELL" =~ "bash" ]]; then 60 | echo -e "${YELLOW}You aren't using bash... This install script (and ${LICYAN}update${YELLOW}) is written in bash, so you might have some problems.${NC}" 61 | fi 62 | 63 | case $(uname) in 64 | Linux) 65 | if [[ "$(cat /etc/*-release || cat /etc/issue || lsb_release -a)" =~ "debian" ]] || [[ "$(cat /etc/*-release || cat /etc/issue || lsb_release -a)" =~ "Debian" ]] || [[ "$(cat /etc/*-release || cat /etc/issue || lsb_release -a)" =~ "ubuntu" ]] || [[ "$(cat /etc/*-release || cat /etc/issue || lsb_release -a)" =~ "Ubuntu" ]] || [[ "$(cat /etc/*-release || cat /etc/issue || lsb_release -a)" =~ "raspbian" ]] || [[ "$(cat /etc/*-release || cat /etc/issue || lsb_release -a)" =~ "Raspbian" ]] || command -v apt-get &>/dev/null || command -v apt &>/dev/null; then 66 | distro="debian" 67 | elif [[ "$(cat /etc/*-release || cat /etc/redhat-release || cat /etc/issue || lsb_release -a)" =~ "fedora" ]] || [[ "$(cat /etc/*-release || cat /etc/redhat-release || cat /etc/issue || lsb_release -a)" =~ "Fedora" ]] || [[ "$(cat /etc/*-release || cat /etc/redhat-release || cat /etc/issue || lsb_release -a)" =~ "CentOS" ]] || [[ "$(cat /etc/*-release || cat /etc/redhat-release || cat /etc/issue || lsb_release -a)" =~ "centos" ]] || [[ "$(cat /etc/*-release || cat /etc/redhat-release || cat /etc/issue || lsb_release -a)" =~ "Red Hat" ]] || [[ "$(cat /etc/*-release || cat /etc/redhat-release || cat /etc/issue || lsb_release -a)" =~ "red hat" ]] || command -v dnf &>/dev/null; then 68 | distro="fedora" 69 | elif [[ "$(cat /etc/*-release || lsb_release -a || cat /etc/issue)" =~ "Arch" ]] || [[ "$(cat /etc/*-release || lsb_release -a || cat /etc/issue)" =~ "arch" ]] || [[ "$(cat /etc/*-release || lsb_release -a || cat /etc/issue)" =~ "Manjaro" ]] || [[ "$(cat /etc/*-release || lsb_release -a || cat /etc/issue)" =~ "manjaro" ]] || command -v pacman &>/dev/null; then 70 | distro="arch" 71 | fi 72 | 73 | case $distro in 74 | "debian") 75 | rm -f update*.deb 76 | printf "\n${WHITE}Downloading ${CYAN}${BOLD}update${NC}${WHITE}...${NC}\n\n" 77 | LATEST=$(curl -s https://api.github.com/repos/Crilum/update/releases/latest | grep -oP '"tag_name": "\K(.*)(?=")') 78 | curl -s https://api.github.com/repos/Crilum/update/releases/latest | 79 | grep browser_download_url | 80 | grep 'all.deb"' | 81 | cut -d '"' -f 4 | 82 | xargs -n 1 curl -L -s -o update_${LATEST}_all.deb 83 | if command -v update &>/dev/null; then 84 | printf "\n${WHITE}Uninstalling update...${NC}" 85 | $sudo apt remove -y update 86 | printf "\n${GREEN}Done!${NC}" 87 | fi 88 | printf "\n${WHITE}Installing update...${NC}" 89 | $sudo apt install -yf ./update_${LATEST}_all.deb 90 | printf "\n${GREEN}Done!${NC}\n" 91 | rm update_${LATEST}_all.deb 92 | ;; 93 | "fedora") 94 | if command -v dnf &>/dev/null; then 95 | pkg_manager="dnf" 96 | elif command -v yum &>/dev/null; then 97 | pkg_manager="yum" 98 | else 99 | echo "No suitable package manager found!! Exiting..."; exit 1 100 | fi 101 | rm -f update*.rpm 102 | printf "\n${WHITE}Downloading ${CYAN}${BOLD}update${NC}${WHITE}...${NC}\n\n" 103 | LATEST=$(curl -s https://api.github.com/repos/Crilum/update/releases/latest | grep -oP '"tag_name": "\K(.*)(?=")') 104 | curl -s https://api.github.com/repos/Crilum/update/releases/latest | 105 | grep browser_download_url | 106 | grep 'noarch.rpm"' | 107 | cut -d '"' -f 4 | 108 | xargs -n 1 curl -L -s -o update-${LATEST}-1.noarch.rpm 109 | if command -v update &>/dev/null; then 110 | printf "\n${WHITE}Uninstalling update...${NC}" 111 | $sudo $pkg_manager remove -y update 112 | printf "\n${GREEN}Done!${NC}" 113 | fi 114 | printf "\n${WHITE}Installing update...${NC}" 115 | $sudo $pkg_manager install ./update-${LATEST}-1.noarch.rpm -y 116 | printf "\n${GREEN}Done!${NC}\n" 117 | rm update-${LATEST}-1.noarch.rpm 118 | ;; 119 | *) 120 | if ! command -v curl &>/dev/null || ! command -v chmod &>/dev/null || ! command -v wget &>/dev/null || ! command -v git &>/dev/null; then 121 | echo -e "${LIRED}Error: Missing dependencies! Please install \`curl\`, \`wget\`, \`git\`, and of course, \`bash\` (If you got this far, you should already have it installed).${NC}" 122 | exit 1 123 | fi 124 | LATEST=$(curl -s https://api.github.com/repos/Crilum/update/releases/latest | grep -oP '"tag_name": "\K(.*)(?=")') 125 | printf "\n${WHITE}Downloading ${CYAN}${BOLD}update${NC}${WHITE}...${NC}\n\n" 126 | cd /tmp/ 127 | git clone https://github.com/Crilum/update -b $LATEST 128 | cd /tmp/update 129 | $sudo cp -f update /usr/bin/ 130 | $sudo ln -sf /usr/bin/update /usr/bin/up 131 | $sudo chmod +x /usr/bin/update /usr/bin/up 132 | ;; 133 | esac 134 | ;; 135 | Darwin) 136 | if ! command -v curl &>/dev/null || ! command -v chmod &>/dev/null || ! command -v wget &>/dev/null || ! command -v git &>/dev/null; then 137 | if ! command -v homebrew &>/dev/null; then 138 | printf "\n${WHITE}Update needs some dependencies (curl, chmod, git, and wget). Do you want to install Homebrew (for installing dependencies)? [Y/n] ${LIBLUE}" 139 | read instHomebrew 140 | if [[ $instHomebrew =~ "yYYesyesYES" ]]; then 141 | /bin/bash -c "$(curl -fsSL https://raw.githubusercontent.com/Homebrew/install/HEAD/install.sh)" 142 | else 143 | printf "\n${RED}User error: user chose not to install Homebrew!" 144 | exit 1 145 | fi 146 | fi 147 | printf "\n${WHITE}Installing dependencies with Homebrew...${NC}\n\n" 148 | brew install curl chmod wget git 149 | fi 150 | LATEST=$(curl -s https://api.github.com/repos/Crilum/update/releases/latest | grep -oP '"tag_name": "\K(.*)(?=")') 151 | printf "\n${WHITE}Downloading ${CYAN}${BOLD}update${NC}${WHITE}...${NC}\n\n" 152 | cd /tmp/ 153 | git clone https://github.com/Crilum/update -b $LATEST 154 | cd /tmp/update 155 | $sudo cp update /usr/local/bin/ 156 | $sudo ln -s /usr/local/bin/update /usr/local/bin/up 157 | $sudo chmod +x /usr/local/bin/update /usr/local/bin/up 158 | ;; 159 | *) 160 | echo "${LIRED}Error: you are not running a suppoted system (supported systems are: Linux or MacOS)! If you are, please file a bug report at https://github.com/Crilum/update/issues/new.${NC}" 161 | exit 1 162 | ;; 163 | esac 164 | 165 | printf "${GREEN}All finished installing!\n${WHITE}Try \'${CYAN}${BOLD}update ${YELLOW}help${WHITE}\' (or, \'${LICYAN}up${NC} ${YELLOW}help${WHITE}\') to learn how to use ${CYAN}${BOLD}update${WHITE}!${NC}\n" 166 | -------------------------------------------------------------------------------- /rpm/README.md: -------------------------------------------------------------------------------- 1 | # Building the RPM package 2 | 3 | To build an rpm package, run the following command from the core of the repository. 4 | 5 | ``` 6 | $ ./rpm/build.sh 7 | ``` 8 | 9 | -------------------------------------------------------------------------------- /rpm/build.sh: -------------------------------------------------------------------------------- 1 | #!/usr/bin/env bash 2 | 3 | # This script will package the `update` script into a `rpm` package. 4 | 5 | declare -r NAME="update" 6 | declare -r BUILD_DIR="$(pwd)" 7 | declare -r VERSION="$(grep "version=" "${BUILD_DIR}/${NAME}" | cut -d"\"" -f2 | cut -d"v" -f2)" 8 | 9 | echo "name: $NAME, build dir: $BUILD_DIR, version: $VERSION, Dir contents:"; ls; echo "../ contents:"; ls ../; ls ../../; file "${BUILD_DIR}/${NAME}" 10 | 11 | if command -v dnf &>/dev/null; then 12 | command -v rpmdev-setuptree &> /dev/null && command -v rpmbuild &>/dev/null || sudo dnf install rpm-build rpmdevtools -y 13 | elif command -v yum &>/dev/null; then 14 | command -v rpmdev-setuptree &> /dev/null && command -v rpmbuild &>/dev/null || sudo yum install rpm-build rpmdevtools -y 15 | elif command -v apt &>/dev/null; then 16 | command -v rpmbuild &>/dev/null || sudo apt install rpm -y 17 | else 18 | printf 'No suitable package manager found!! Exiting...' 19 | exit 1 20 | fi 21 | 22 | # Exit out when running the script as root. 23 | if [[ ${UID} -eq 0 ]]; then 24 | printf 'Please run this script as a normal user.' 25 | exit 1 26 | fi 27 | 28 | # Create the necessary directories. 29 | mkdir -p "${HOME}/rpmbuild/"{BUILD,BUILDROOT,RPMS,SOURCES,SPECS,SRPMS} 30 | mkdir -p "${HOME}/rpmbuild/BUILD/${NAME}-${VERSION}" 31 | mkdir -p "${BUILD_DIR}/${NAME}-${VERSION}" 32 | 33 | # Create the tarball. 34 | echo "Creating tarball..." 35 | cp -r "${BUILD_DIR}/${NAME}" "${BUILD_DIR}/${NAME}-${VERSION}" 36 | echo "Done!"; ls "${BUILD_DIR}/${NAME}-${VERSION}/" 37 | tar --create --file "${NAME}-${VERSION}.tar.gz" "${NAME}-${VERSION}" 38 | 39 | # Move the tarball to the SOURCES directory. 40 | mv "${BUILD_DIR}/${NAME}-${VERSION}.tar.gz" "${HOME}/rpmbuild/SOURCES/" 41 | 42 | # Update the version number. 43 | sed -i "s/VERSION THE SCRIPT WILL UPDATE THIS!/${VERSION}/g" "${BUILD_DIR}/rpm/${NAME}.spec" 44 | 45 | # Copy over the spec file. 46 | cp -r "${BUILD_DIR}/rpm/${NAME}.spec" "${HOME}/rpmbuild/SPECS/${NAME}.spec" 47 | 48 | # build RPM package. 49 | rpmbuild -ba "${HOME}/rpmbuild/SPECS/${NAME}.spec" 50 | 51 | # Cleanup 52 | rm -rf "${NAME}-${VERSION}" 53 | 54 | -------------------------------------------------------------------------------- /rpm/update.spec: -------------------------------------------------------------------------------- 1 | Name: update 2 | Version: VERSION THE SCRIPT WILL UPDATE THIS! 3 | Release: 1%{?dist} 4 | BuildArch: noarch 5 | URL: https://github.com/Crilum/%{name} 6 | Summary: Updates apps/packages/dependencies from Apt, Pi-Apps, Flatpak, the Snap Store, Homebrew, and NPM. 7 | 8 | License: GPLv3 9 | Source0: %{name}-%{version}.tar.gz 10 | 11 | Requires: bash 12 | Requires: curl 13 | Requires: wget 14 | 15 | %description 16 | Updates apps/packages/dependencies from Apt, Pi-Apps, Flatpak, the Snap Store, Homebrew, and NPM. 17 | 18 | %prep 19 | %setup -q 20 | 21 | %install 22 | rm -rf $RPM_BUILD_ROOT 23 | mkdir -p $RPM_BUILD_ROOT/%{_bindir} 24 | cp %{name} $RPM_BUILD_ROOT/%{_bindir} 25 | 26 | %post 27 | [[ -L %{_bindir}/up ]] && rm -rf %{_bindir}/up 28 | [[ $(ls -l $(command -v up)) =~ "/usr/bin/update" ]] || ln -v -s /usr/bin/update "/usr/bin/up" 29 | 30 | %postun 31 | [[ -L %{_bindir}/up ]] && rm -rf %{_bindir}/up 32 | exit 0 33 | 34 | %clean 35 | rm -rf $RPM_BUILD_ROOT 36 | 37 | %files 38 | %{_bindir}/%{name} 39 | 40 | -------------------------------------------------------------------------------- /update: -------------------------------------------------------------------------------- 1 | #!/bin/bash 2 | 3 | version="v1.4.5" 4 | 5 | #Color Variables 6 | 7 | NC='\e[0m' 8 | BLACK='\e[0;30m' 9 | RED='\e[0;31m' 10 | GREEN='\e[0;32m' 11 | WHITE='\e[1;37m' 12 | ORANGE='\e[0;33m' 13 | BLUE='\e[0;34m' 14 | PURPLE='\e[0;35m' 15 | CYAN='\e[0;36m' 16 | YELLOW='\e[1;33m' 17 | DARGRAY='\e[1;30m' 18 | 19 | #Lighter Colors 20 | LIGRAY='\e[0;37m' 21 | LIGREEN='\e[1;32m' 22 | LIRED='\e[1;31m' 23 | LIBLUE='\e[1;34m' 24 | LIPURPLE='\e[1;35m' 25 | LICYAN='\e[1;36m' 26 | 27 | #Background Color Variables 28 | 29 | BACKBLACK='\e[0;40m' 30 | BACKRED='\e[0;41m' 31 | BACKGREEN='\e[0;42m' 32 | BACKWHITE='\e[1;47m' 33 | BACKORANGE='\e[0;43m' 34 | BACKBLUE='\e[0;44m' 35 | BACKPURPLE='\e[0;45m' 36 | BACKCYAN='\e[0;46m' 37 | BACKYELLOW='\e[1;43m' 38 | 39 | #Lighter Colors 40 | BACKLIGRAY='\e[0;47m' 41 | BACKLIGREEN='\e[1;42m' 42 | BACKLIRED='\e[1;41m' 43 | BACKLIBLUE='\e[1;44m' 44 | BACKLIPURPLE='\e[1;45m' 45 | BACKLICYAN='\e[1;46m' 46 | 47 | #Markup Variables 48 | UNDERLINE='\e[4m' 49 | DOUBLEUNDERLINE='\e[21m' 50 | BOLD='\e[1m' 51 | BLINK='\e[5m' 52 | REVVID='\e[7m' 53 | 54 | pkgs="$*" 55 | if [[ "$pkgs" =~ "--no-grep-args" ]]; then 56 | pkgs="$(echo $pkgs | sed -e 's/--no-grep-args//g' -e 's/--all//g' -e 's/-a//g' -e 's/--apt//g' -e 's/-A//g' -e 's/all//g' -e 's/--npm//g' -e 's/-n//g' -e 's/snaps//g' -e 's/-s//g' -e 's/--snaps//g' -e 's/-f//g' -e 's/--flatpak//g' -e 's/-d//g' -e 's/--dnf//g')" 57 | else 58 | pkgs="$(echo $pkgs | sed -e 's/--no-grep-args//g' -e 's/--all//g' -e 's/-a//g' -e 's/--apt//g' -e 's/apt//g' -e 's/-A//g' -e 's/all//g' -e 's/npm//g' -e 's/--npm//g' -e 's/-n//g' -e 's/snaps//g' -e 's/-s//g' -e 's/--snaps//g' -e 's/flatpak//g' -e 's/-f//g' -e 's/--flatpak//g' -e 's/dnf//g' -e 's/-d//g' -e 's/--dnf//g')" 59 | fi 60 | # Functions 61 | 62 | function error() { 63 | if [ "$*" == "-n" ] || [ "$*" == "--no-exit" ]; then 64 | printf "\n${RED}${BOLD}Error: $1${NC}\n" 65 | else 66 | printf "\n${RED}${BOLD}Error: $1${NC}\n" 67 | exit 1 68 | fi 69 | } 70 | 71 | function warning() { 72 | printf "\nWarning: ${YELLOW}$1${NC}\n" 73 | } 74 | 75 | function status() { 76 | if [ "$1" == "-g" ] || [ "$1" == "--green" ]; then 77 | printf "\n${GREEN}$2${NC}\n" 78 | elif [ "$1" == "-c" ] || [ "$1" == "--cyan" ]; then 79 | printf "\n${CYAN}$2${NC}\n" 80 | elif [ "$1" == "-C" ] || [ "$1" == "--cyan-bold" ]; then 81 | printf "\n${LICYAN}$2${NC}\n" 82 | else 83 | printf "\n${WHITE}$1${NC}\n" 84 | fi 85 | } 86 | 87 | function internet_check() { 88 | if ! command -v wget &>/dev/null; then 89 | error "\`wget\` isn't installed! wget is required to perform connection tests. Please install wget." 90 | elif ! wget --spider "https://github.com" &>/dev/null; then 91 | error "I tried to contact ${BLUE}${BOLD}https://github.com${LIRED} but it did not respond! Check your internet connection!" 92 | fi 93 | } 94 | 95 | function upd_pi_apps() { 96 | status 'Pi-Apps output:' 97 | 98 | if [ "$(whoami)" = "root" ]; then 99 | echo -e "\n\e[1;31mError: you can't update Pi-Apps as root! Please try again as normal user.\e[0m" 100 | return 1 101 | fi 102 | 103 | if [ ! -d $HOME/pi-apps ]; then 104 | if [[ $(cat /proc/cpuinfo | grep "Raspberry Pi") =~ "Raspberry Pi" ]]; then 105 | warning 'No Pi-Apps directory found! Do you want to install Pi-Apps? Timeout in 15 seconds... [y/n] ' 106 | read -t 15 input 107 | case $input in 108 | y | Y | yes | Yes | YES) wget -qO- https://raw.githubusercontent.com/Botspot/pi-apps/master/install | bash || error '\nI was not able to download and run the Pi-Apps install script. Make sure you have wget installed, and an internet connection.' ;; 109 | *) status 'Ok, I will not install Pi-Apps.' || exit 0 ;; 110 | esac 111 | elif [[ ! $(cat /proc/cpuinfo | grep "Raspberry Pi") =~ "Raspberry Pi" ]] || [[ ! $(arch) =~ "arm" ]] && [[ ! $(arch) =~ "aarch" ]] && [[ ! "$(uname)" == "Darwin" ]]; then 112 | if [ "$1" == "all" ]; then 113 | warning "I didn't find Pi-Apps, and you are not using a Raspberry Pi, or an ARM computer (your architecture is $(arch)), so I won't ask to install Pi-Apps." 114 | else 115 | error "I didn't find Pi-Apps, and you are not using a Raspberry Pi, or an ARM computer (your architecture is $(arch)), so I won't ask to install Pi-Apps." 116 | fi 117 | fi 118 | elif [ ! -e $HOME/pi-apps/updater ]; then 119 | error 'I couldn'\''t find the pi-apps updater script.. Something is wrong!\n' 120 | fi 121 | 122 | $HOME/pi-apps/updater cli-yes 123 | status "Setting status..." 124 | $HOME/pi-apps/updater set-status &>/dev/null 125 | status -g "Done!" 126 | } 127 | 128 | function upd_snaps() { 129 | 130 | if ! command -v snap &>/dev/null; then 131 | status "I couldn't find snapd on your system, so I'm not using it." 132 | return 133 | fi 134 | if [ "$1" == "all" ]; then 135 | status 'Checking for snap updates. Please Wait...\n' 136 | $sudo snap refresh || warning 'I failed to run '\''snap refresh'\''! snap has probably output an error above.' 137 | else 138 | internet_check 139 | if [ "$pkgs" != "" ]; then 140 | errMsg="I wasn't able to refresh: $pkgs!" 141 | else 142 | errMsg="I wasn't able to refresh snap containers!" 143 | fi 144 | status 'Checking for snap updates. Please Wait...\n' 145 | $sudo snap refresh $pkgs || error "$errMsg" 146 | fi 147 | } 148 | 149 | function upd_upd_script() { 150 | internet_check 151 | if [ "$1" != "on-start" ]; then 152 | status 'Checking for an update...' 153 | fi 154 | latestRelease="$(curl --silent https://api.github.com/repos/Crilum/update/releases/latest | grep "tag_name" | sed -e 's/"//g' -e 's/://g' -e 's/,//g' -e 's/tag_name//g' -e 's/ //g' -e 's/v//')" 155 | versionNoV="$(echo $version | sed -e 's/v//')" 156 | updateAvailable="no" 157 | if [ "$latestRelease" \> "$versionNoV" ]; then 158 | if [ "$1" == "on-start" ]; then 159 | status -C "There's an update available! ${WHITE}Run ${LICYAN}update ${YELLOW}-u${WHITE} to install it." 160 | updateAvailable="yes" 161 | else 162 | echo -en "${LICYAN}There's an update available! Do you want to install it? [Y/n] " 163 | read confInstallUpdate 164 | updateAvailable="yes" 165 | case $confInstallUpdate in 166 | y | Y | yes | YES | Yes | "") 167 | curl --silent "https://raw.githubusercontent.com/Crilum/update/main/install" | bash || error 'I couldn'\''t update ${CYAN}${BOLD}update${RED}! Please make sure you have curl installed!' 168 | updateAvailable="no" 169 | ;; 170 | *) 171 | status "Ok, I won't install the update." 172 | exit 0 173 | ;; 174 | esac 175 | fi 176 | elif [ "$latestRelease" \< "$versionNoV" ]; then 177 | if [ "$1" != "on-start" ]; then 178 | status -g "Looks like you're developing an update, and haven't released it yet. ${LICYAN}Cool${WHITE}!\n(Or your version got messed up somehow...)" 179 | updateAvailable="no" 180 | fi 181 | updateAvailable="no" 182 | elif [ "$latestRelease" == "$versionNoV" ]; then 183 | if [ "$1" == "on-start" ]; then 184 | updateAvailable="no" 185 | return 186 | else 187 | status -g "No updates available. You're good to go!" 188 | fi 189 | 190 | fi 191 | } 192 | 193 | function upd_flatpak() { 194 | if ! command -v flatpak &>/dev/null; then 195 | status "I couldn't find Flatpak on your system, so I'm not using it." 196 | return 197 | fi 198 | if [ "$1" == "all" ]; then 199 | status '\nFlatpak output:\n' 200 | flatpak update -y || warning 'I couldn'\''t update flatpak apps! flatpak will probably have an error above.' 201 | else 202 | if [ "$pkgs" != "" ]; then 203 | errMsg="I wasn't able to upgrade: $pkgs!" 204 | else 205 | errMsg="I wasn't able to upgrade Flatpak apps!" 206 | fi 207 | status '\nFlatpak output:\n' 208 | flatpak update $pkgs -y || error "$errMsg" 209 | fi 210 | } 211 | 212 | function upd_pacman() { 213 | if ! command -v pacman &>/dev/null; then 214 | status "I couldn't find pacman, so I'm assuming you're not running Arch or a derivative of it. Not using pacman." 215 | return 216 | fi 217 | if [ "$1" == "all" ]; then 218 | status 'pacman output:\n' 219 | $sudo pacman -Syu || warning "I couldn't update pacman packages!" 220 | else 221 | status 'pacman output:\n' 222 | $sudo pacman -Syu || error "I couldn't update pacman packages!" 223 | fi 224 | } 225 | 226 | function upd_apt() { 227 | if ! command -v apt &>/dev/null; then 228 | status "I couldn't find apt, so I'm assuming you're not running Debian or a derivative of it. Not using apt." 229 | return 230 | fi 231 | if [ "$1" == "all" ]; then 232 | status '\nApt output:\n' 233 | $sudo apt update 234 | $sudo apt -y upgrade 235 | $sudo apt -y autoremove 236 | else 237 | if [ "$pkgs" != "" ]; then 238 | errMsg="I wasn't able to upgrade: $pkgs!" 239 | else 240 | errMsg="I wasn't able to upgrade apt packages!" 241 | fi 242 | internet_check 243 | status '\nApt output:\n' 244 | $sudo apt update || error "Failed to run 'apt update'!" 245 | $sudo apt -y upgrade $pkgs || error "$errMsg" 246 | $sudo apt -y autoremove 247 | fi 248 | } 249 | 250 | function upd_homebrew() { 251 | if ! brew help &>/dev/null; then 252 | status "I couldn't find Homebrew on your system, so I'm not using it." 253 | return 254 | fi 255 | if [ "$1" == "all" ]; then 256 | printf "\n${WHITE}Homebrew output:${NC}\n" 257 | brew update || warning "Homebrew failed to update its formulae!" 258 | brew upgrade || warning "Homebrew failed to upgrade its casks and formulae!" 259 | else 260 | internet_check 261 | printf "\n${WHITE}Homebrew output:${NC}\n" 262 | brew update || error "Homebrew failed to update its formulae!" 263 | brew upgrade || error "Homebrew failed to upgrade its casks and formulae!" 264 | fi 265 | } 266 | 267 | function upd_npm() { 268 | if ! command -v npm &>/dev/null; then 269 | status "I couldn't find NPM on your system, so I'm not using it." 270 | return 271 | fi 272 | if [ "$1" == "all" ]; then 273 | warning 'Updating npm dependencies should only be done if you know what you'\''re doing. Do you want to continue? Timeout in 10 seconds... [y/N] ' 274 | read -t 10 input 275 | case $input in 276 | y | Y | Yes | yes | YES | "") 277 | printf "\n${WHITE}npm output:${NC}\n" 278 | npm update 279 | ;; 280 | n | N | No | no | NO | *) status -C "Ok, I won't update npm." ;; 281 | esac 282 | else 283 | warning 'Updating npm dependencies should only be done if you know what you'\''re doing. Do you want to continue? [y/N] ' 284 | read input 285 | case $input in 286 | y | Y | Yes | yes | YES | "") 287 | printf "\n${WHITE}npm output:${NC}\n" 288 | npm update $pkgs 289 | ;; 290 | n | N | No | no | NO | *) status -C "Ok, I won't update npm." ;; 291 | esac 292 | fi 293 | } 294 | 295 | function upd_dnf() { 296 | if command -v dnf &>/dev/null; then 297 | pkg_manager="dnf" 298 | elif command -v yum &>/dev/null; then 299 | pkg_manager="yum" 300 | else 301 | status "I couldn't find dnf (or yum), so I'm assuming you're not running Fedora or a derivative of it. Not using dnf." 302 | return 303 | fi 304 | if [ "$1" == "all" ]; then 305 | $sudo $pkg_manager upgrade $pkgs 306 | else 307 | internet_check 308 | $sudo $pkg_manager upgrade $pkgs 309 | fi 310 | } 311 | function upd_all() { 312 | internet_check 313 | upd_apt all 314 | upd_homebrew all 315 | upd_pacman all 316 | upd_dnf all 317 | # Updating with npm is disabled by default. Uncomment the next line to enable it. 318 | #npm update all 319 | upd_flatpak all 320 | upd_snaps all 321 | upd_pi_apps all 322 | } 323 | 324 | function help() { 325 | 326 | echo -e "\n${LICYAN}update ${WHITE}version ${YELLOW}${version} ${WHITE}| created by ${LIBLUE}Crilum\n 327 | ${WHITE}Usage: ${CYAN}${BOLD}update${NC} ${YELLOW}${BOLD}OPTIONS${NC}${WHITE} 328 | 329 | These are the main options/arguments for ${CYAN}${BOLD}update${NC}${WHITE}: 330 | 331 | ${CYAN}${BOLD}update${YELLOW}${BOLD} apt · -a · --apt [packages]${NC} ${WHITE}Updates apt packages 332 | ${CYAN}${BOLD}update ${YELLOW}${BOLD}all · -A · --all${NC} ${WHITE}Updates apps on all installed package managers and/or app stores that are supported ${NC}- ${LIRED}Note: This option does not update NPM packages because this can cause trouble. 333 | ${CYAN}${BOLD}update${NC} ${YELLOW}${BOLD}pi-apps · -p · --pi-apps${NC} ${WHITE}Updates Pi-Apps, and apps installed with Pi-Apps 334 | ${CYAN}${BOLD}update ${YELLOW}${BOLD}npm · -n · --npm${NC} ${WHITE}Updates all npm packages 335 | ${CYAN}${BOLD}update${NC} ${YELLOW}${BOLD}snaps · -s · --snaps [snaps]${NC} ${WHITE}Updates snaps with snapd 336 | ${CYAN}${BOLD}update${NC} ${YELLOW}${BOLD}flatpak · -f · --flatpak [packages] ${NC}${WHITE}Updates flatpak apps 337 | ${CYAN}${BOLD}update${NC} ${YELLOW}${BOLD}homebrew · -H · --homebrew${NC} ${WHITE}Updates Homebrew apps 338 | ${CYAN}${BOLD}update${NC} ${YELLOW}${BOLD}pacman · -c · --pacman [packages] ${NC}${WHITE}Updates pacman apps 339 | ${CYAN}${BOLD}update${NC} ${YELLOW}${BOLD}dnf · -d · --dnf${NC} ${WHITE}Updates dnf packages (or yum, if your OS is that old) 340 | ${CYAN}${BOLD}update ${YELLOW}${BOLD}self-update · -u · --self-update${NC} ${WHITE}Updates the ${CYAN}${BOLD}update ${WHITE}script 341 | ${CYAN}${BOLD}update${NC} ${YELLOW}${BOLD}help · -h · --help${NC} ${WHITE}Displays this help 342 | ${CYAN}${BOLD}update${NC} ${YELLOW}${BOLD}version · -v · --version${NC} ${WHITE}Prints version 343 | 344 | flags for ${LICYAN}update${WHITE}: 345 | 346 | ${YELLOW}${BOLD}--no-grep-args${NC} ${WHITE}If this flag is specified, ${LICYAN}update${WHITE} won't remove arguments that are also packages from the update package list, i.e. 'apt' 347 | ${NC}" 348 | if [ "$(whoami)" == "root" ]; then 349 | echo -e "${LIRED}Note: \`${LICYAN}update${LIRED}\` is not meant to be run with \`${WHITE}sudo${LIRED}\`. Although \`${LICYAN}update${LIRED}\` can be run with \`${WHITE}sudo${LIRED}\`, it is not recommended.\n${NC}" 350 | fi 351 | upd_upd_script on-start 352 | } 353 | 354 | # Script 355 | 356 | if [ "$(whoami)" == "root" ]; then 357 | sudo="" 358 | else 359 | sudo="sudo" 360 | fi 361 | 362 | case $1 in 363 | version | -v | --version) ;; 364 | help | -h | --help | \?) ;; 365 | self-update | -u | --self-update) ;; 366 | *) upd_upd_script on-start ;; 367 | esac 368 | 369 | case $1 in 370 | help | --help | -h) help ;; 371 | all | -A | --all) 372 | printf "${CYAN}${BOLD}\nWelcome to Crilum\'s Update Script!\n${NC}" 373 | upd_all 374 | ;; 375 | self-update | -u | --self-update) upd_upd_script ;; 376 | snaps | -s | --snaps) 377 | printf "${CYAN}${BOLD}\nWelcome to Crilum\'s Update Script!\n${NC}" 378 | upd_snaps 379 | ;; 380 | homebrew | -H | --homebrew) 381 | printf "${CYAN}${BOLD}\nWelcome to Crilum\'s Update Script!\n${NC}" 382 | upd_homebrew 383 | ;; 384 | pi-apps | -p | --pi-apps) 385 | printf "${CYAN}${BOLD}\nWelcome to Crilum\'s Update Script!\n${NC}" 386 | upd_pi_apps 387 | ;; 388 | flatpak | -f | --flatpak) 389 | printf "${CYAN}${BOLD}\nWelcome to Crilum\'s Update Script!\n${NC}" 390 | upd_flatpak 391 | ;; 392 | npm | -n | --npm) 393 | printf "${CYAN}${BOLD}\nWelcome to Crilum\'s Update Script!\n${NC}" 394 | upd_npm 395 | ;; 396 | pacman | -c | --pacman) 397 | printf "${CYAN}${BOLD}\nWelcome to Crilum\'s Update Script!\n${NC}" 398 | upd_pacman 399 | ;; 400 | apt | -a | --apt) 401 | printf "${CYAN}${BOLD}\nWelcome to Crilum\'s Update Script!\n${NC}" 402 | upd_apt 403 | ;; 404 | dnf | -d | --dnf) 405 | printf "${CYAN}${BOLD}\nWelcome to Crilum\'s Update Script!\n${NC}" 406 | upd_dnf 407 | ;; 408 | version | -v | --version) echo -e "${LICYAN}${version}${NC}" ;; 409 | *) printf "${CYAN}${BOLD}\nWelcome to Crilum\'s Update Script!\n${NC}" 410 | upd_all 411 | ;; 412 | esac 413 | --------------------------------------------------------------------------------