From b65c3f018f500e488ae8ffd1c3067bece4e371ac Mon Sep 17 00:00:00 2001 From: Syndamia Date: Mon, 23 May 2022 11:36:01 +0300 Subject: Added general information and current status of the project --- README.md | 94 +++++++++++++++------------------------------------------------ 1 file changed, 22 insertions(+), 72 deletions(-) diff --git a/README.md b/README.md index 51436da..41a4b4d 100644 --- a/README.md +++ b/README.md @@ -1,92 +1,42 @@ # stupid -The stupid package manager for Linux +stupid is a dead simple "packet" manager, designed more as manual automation than anything else. In brief, each package file has two bash functions, one for installing and one for removing, which are ran when installing or removing a package. -## Getting started +**Do NOT use simple with other people's package files!** As mentioned, these functions are ran as-is, as the root user. This could very easily do something malicious to your system. -To make it easy for you to get started with GitLab, here's a list of recommended next steps. +**simple must not be used as a replacement to any other package manager!** It is fairly obvious why, but it doesn't (and won't) have many lifesaving features most package managers have. Also, package files cannot be trusted. -Already a pro? Just edit this README.md and make it your own. Want to make it easy? [Use the template at the bottom](#editing-this-readme)! +### Why would I want to use this? -## Add your files +In an ideal world, you shouldn't (hence the name), you should configure a local repository with packages for your actual package manager. -- [ ] [Create](https://docs.gitlab.com/ee/user/project/repository/web_editor.html#create-a-file) or [upload](https://docs.gitlab.com/ee/user/project/repository/web_editor.html#upload-a-file) files -- [ ] [Add files using the command line](https://docs.gitlab.com/ee/gitlab-basics/add-file.html#add-a-file-using-the-command-line) or push an existing Git repository with the following command: +But, that isn't always straight forward and could consume too much time. Also, it is not impossible your packet manager just doesn't support the exact way you want to install a package. -``` -cd existing_repo -git remote add origin https://gitlab.com/Syndamia/stupid.git -git branch -M main -git push -uf origin main -``` +stupid is a compromise, it's worse than just configuring your actual package manager, but it is a bit better than arbitrarily installing a package and then forgetting how to remove it a month later. -## Integrate with your tools +## Dependencies -- [ ] [Set up project integrations](https://gitlab.com/Syndamia/stupid/-/settings/integrations) +stupid is nothing more than a bash script, so all of it's requirements are certain basic commands, which should mostly come with your distribution. -## Collaborate with your team +`bash`, `echo`, `mkdir`, `cd`, `tail`, `grep`, `find`, `cat` -- [ ] [Invite team members and collaborators](https://docs.gitlab.com/ee/user/project/members/) -- [ ] [Create a new merge request](https://docs.gitlab.com/ee/user/project/merge_requests/creating_merge_requests.html) -- [ ] [Automatically close issues from merge requests](https://docs.gitlab.com/ee/user/project/issues/managing_issues.html#closing-issues-automatically) -- [ ] [Enable merge request approvals](https://docs.gitlab.com/ee/user/project/merge_requests/approvals/) -- [ ] [Automatically merge when pipeline succeeds](https://docs.gitlab.com/ee/user/project/merge_requests/merge_when_pipeline_succeeds.html) +### How to install -## Test and Deploy +TBD -Use the built-in continuous integration in GitLab. +## How to use -- [ ] [Get started with GitLab CI/CD](https://docs.gitlab.com/ee/ci/quick_start/index.html) -- [ ] [Analyze your code for known vulnerabilities with Static Application Security Testing(SAST)](https://docs.gitlab.com/ee/user/application_security/sast/) -- [ ] [Deploy to Kubernetes, Amazon EC2, or Amazon ECS using Auto Deploy](https://docs.gitlab.com/ee/topics/autodevops/requirements.html) -- [ ] [Use pull-based deployments for improved Kubernetes management](https://docs.gitlab.com/ee/user/clusters/agent/) -- [ ] [Set up protected environments](https://docs.gitlab.com/ee/ci/environments/protected_environments.html) +TBD -*** +## Creating your own package files -# Editing this README +**All** package files are named in the format `PACKAGENAME--VERSION.stupid`. -When you're ready to make this README your own, just edit this file and use the handy template below (or feel free to structure it however you want - this is just a starting point!). Thank you to [makeareadme.com](https://www.makeareadme.com/) for this template. +TBC -## Suggestions for a good README -Every project is different, so consider which of these sections apply to yours. The sections used in the template are suggestions for most open source projects. Also keep in mind that while a README can be too long and detailed, too long is better than too short. If you think your README is too long, consider utilizing another form of documentation rather than cutting out information. +## Feature status -## Name -Choose a self-explaining name for your project. - -## Description -Let people know what your project can do specifically. Provide context and add a link to any reference visitors might be unfamiliar with. A list of Features or a Background subsection can also be added here. If there are alternatives to your project, this is a good place to list differentiating factors. - -## Badges -On some READMEs, you may see small images that convey metadata, such as whether or not all the tests are passing for the project. You can use Shields to add some to your README. Many services also have instructions for adding a badge. - -## Visuals -Depending on what you are making, it can be a good idea to include screenshots or even a video (you'll frequently see GIFs rather than actual videos). Tools like ttygif can help, but check out Asciinema for a more sophisticated method. - -## Installation -Within a particular ecosystem, there may be a common way of installing things, such as using Yarn, NuGet, or Homebrew. However, consider the possibility that whoever is reading your README is a novice and would like more guidance. Listing specific steps helps remove ambiguity and gets people to using your project as quickly as possible. If it only runs in a specific context like a particular programming language version or operating system or has dependencies that have to be installed manually, also add a Requirements subsection. - -## Usage -Use examples liberally, and show the expected output if you can. It's helpful to have inline the smallest example of usage that you can demonstrate, while providing links to more sophisticated examples if they are too long to reasonably include in the README. - -## Support -Tell people where they can go to for help. It can be any combination of an issue tracker, a chat room, an email address, etc. - -## Roadmap -If you have ideas for releases in the future, it is a good idea to list them in the README. - -## Contributing -State if you are open to contributions and what your requirements are for accepting them. - -For people who want to make changes to your project, it's helpful to have some documentation on how to get started. Perhaps there is a script that they should run or some environment variables that they need to set. Make these steps explicit. These instructions could also be useful to your future self. - -You can also document commands to lint the code or run tests. These steps help to ensure high code quality and reduce the likelihood that the changes inadvertently break something. Having instructions for running tests is especially helpful if it requires external setup, such as starting a Selenium server for testing in a browser. - -## Authors and acknowledgment -Show your appreciation to those who have contributed to the project. - -## License -For open source projects, say how it is licensed. - -## Project status -If you have run out of energy or time for your project, put a note at the top of the README saying that development has slowed down or stopped completely. Someone may choose to fork your project or volunteer to step in as a maintainer or owner, allowing your project to keep going. You can also make an explicit request for maintainers. +- [ ] Install +- [ ] Remove +- [ ] Query +- [ ] Update -- cgit v1.2.3