Merge branch 'main' into 'main'
create the base of project See merge request tools/boot-manager!1
This commit is contained in:
commit
f3cd7c8254
6 changed files with 305 additions and 93 deletions
162
.gitignore
vendored
Normal file
162
.gitignore
vendored
Normal file
|
|
@ -0,0 +1,162 @@
|
|||
### Python template
|
||||
# Byte-compiled / optimized / DLL files
|
||||
__pycache__/
|
||||
*.py[cod]
|
||||
*$py.class
|
||||
|
||||
# C extensions
|
||||
*.so
|
||||
|
||||
# Distribution / packaging
|
||||
.Python
|
||||
build/
|
||||
develop-eggs/
|
||||
dist/
|
||||
downloads/
|
||||
eggs/
|
||||
.eggs/
|
||||
lib/
|
||||
lib64/
|
||||
parts/
|
||||
sdist/
|
||||
var/
|
||||
wheels/
|
||||
share/python-wheels/
|
||||
*.egg-info/
|
||||
.installed.cfg
|
||||
*.egg
|
||||
MANIFEST
|
||||
|
||||
# PyInstaller
|
||||
# Usually these files are written by a python script from a template
|
||||
# before PyInstaller builds the exe, so as to inject date/other infos into it.
|
||||
*.manifest
|
||||
*.spec
|
||||
|
||||
# Installer logs
|
||||
pip-log.txt
|
||||
pip-delete-this-directory.txt
|
||||
|
||||
# Unit test / coverage reports
|
||||
htmlcov/
|
||||
.tox/
|
||||
.nox/
|
||||
.coverage
|
||||
.coverage.*
|
||||
.cache
|
||||
nosetests.xml
|
||||
coverage.xml
|
||||
*.cover
|
||||
*.py,cover
|
||||
.hypothesis/
|
||||
.pytest_cache/
|
||||
cover/
|
||||
|
||||
# Translations
|
||||
*.mo
|
||||
*.pot
|
||||
|
||||
# Django stuff:
|
||||
*.log
|
||||
local_settings.py
|
||||
db.sqlite3
|
||||
db.sqlite3-journal
|
||||
|
||||
# Flask stuff:
|
||||
instance/
|
||||
.webassets-cache
|
||||
|
||||
# Scrapy stuff:
|
||||
.scrapy
|
||||
|
||||
# Sphinx documentation
|
||||
docs/_build/
|
||||
|
||||
# PyBuilder
|
||||
.pybuilder/
|
||||
target/
|
||||
|
||||
# Jupyter Notebook
|
||||
.ipynb_checkpoints
|
||||
|
||||
# IPython
|
||||
profile_default/
|
||||
ipython_config.py
|
||||
|
||||
# pyenv
|
||||
# For a library or package, you might want to ignore these files since the code is
|
||||
# intended to run in multiple environments; otherwise, check them in:
|
||||
# .python-version
|
||||
|
||||
# pipenv
|
||||
# According to pypa/pipenv#598, it is recommended to include Pipfile.lock in version control.
|
||||
# However, in case of collaboration, if having platform-specific dependencies or dependencies
|
||||
# having no cross-platform support, pipenv may install dependencies that don't work, or not
|
||||
# install all needed dependencies.
|
||||
#Pipfile.lock
|
||||
|
||||
# poetry
|
||||
# Similar to Pipfile.lock, it is generally recommended to include poetry.lock in version control.
|
||||
# This is especially recommended for binary packages to ensure reproducibility, and is more
|
||||
# commonly ignored for libraries.
|
||||
# https://python-poetry.org/docs/basic-usage/#commit-your-poetrylock-file-to-version-control
|
||||
#poetry.lock
|
||||
|
||||
# pdm
|
||||
# Similar to Pipfile.lock, it is generally recommended to include pdm.lock in version control.
|
||||
#pdm.lock
|
||||
# pdm stores project-wide configurations in .pdm.toml, but it is recommended to not include it
|
||||
# in version control.
|
||||
# https://pdm.fming.dev/#use-with-ide
|
||||
.pdm.toml
|
||||
|
||||
# PEP 582; used by e.g. github.com/David-OConnor/pyflow and github.com/pdm-project/pdm
|
||||
__pypackages__/
|
||||
|
||||
# Celery stuff
|
||||
celerybeat-schedule
|
||||
celerybeat.pid
|
||||
|
||||
# SageMath parsed files
|
||||
*.sage.py
|
||||
|
||||
# Environments
|
||||
.env
|
||||
.venv
|
||||
env/
|
||||
venv/
|
||||
ENV/
|
||||
env.bak/
|
||||
venv.bak/
|
||||
|
||||
# Spyder project settings
|
||||
.spyderproject
|
||||
.spyproject
|
||||
|
||||
# Rope project settings
|
||||
.ropeproject
|
||||
|
||||
# mkdocs documentation
|
||||
/site
|
||||
|
||||
# mypy
|
||||
.mypy_cache/
|
||||
.dmypy.json
|
||||
dmypy.json
|
||||
|
||||
# Pyre type checker
|
||||
.pyre/
|
||||
|
||||
# pytype static type analyzer
|
||||
.pytype/
|
||||
|
||||
# Cython debug symbols
|
||||
cython_debug/
|
||||
|
||||
# PyCharm
|
||||
# JetBrains specific template is maintained in a separate JetBrains.gitignore that can
|
||||
# be found at https://github.com/github/gitignore/blob/main/Global/JetBrains.gitignore
|
||||
# and can be added to the global gitignore or merged into this file. For a more nuclear
|
||||
# option (not recommended) you can uncomment the following to ignore the entire idea folder.
|
||||
.idea/
|
||||
|
||||
94
README.md
94
README.md
|
|
@ -1,93 +1 @@
|
|||
# Parch Boot Manager
|
||||
|
||||
|
||||
|
||||
## Getting started
|
||||
|
||||
To make it easy for you to get started with GitLab, here's a list of recommended next steps.
|
||||
|
||||
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)!
|
||||
|
||||
## Add your files
|
||||
|
||||
- [ ] [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:
|
||||
|
||||
```
|
||||
cd existing_repo
|
||||
git remote add origin https://git.parchlinux.com/tools/boot-manager.git
|
||||
git branch -M main
|
||||
git push -uf origin main
|
||||
```
|
||||
|
||||
## Integrate with your tools
|
||||
|
||||
- [ ] [Set up project integrations](https://git.parchlinux.com/tools/boot-manager/-/settings/integrations)
|
||||
|
||||
## Collaborate with your team
|
||||
|
||||
- [ ] [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/)
|
||||
- [ ] [Set auto-merge](https://docs.gitlab.com/ee/user/project/merge_requests/merge_when_pipeline_succeeds.html)
|
||||
|
||||
## Test and Deploy
|
||||
|
||||
Use the built-in continuous integration in GitLab.
|
||||
|
||||
- [ ] [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)
|
||||
|
||||
***
|
||||
|
||||
# Editing this README
|
||||
|
||||
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!). Thanks to [makeareadme.com](https://www.makeareadme.com/) for this template.
|
||||
|
||||
## 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.
|
||||
|
||||
## 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.
|
||||
boot-manager
|
||||
45
src/bootctl.py
Normal file
45
src/bootctl.py
Normal file
|
|
@ -0,0 +1,45 @@
|
|||
from typing import List
|
||||
from os import execv, listdir, path
|
||||
import subprocess
|
||||
|
||||
|
||||
class Entry:
|
||||
def __init__(self, name, entry):
|
||||
self.name = name
|
||||
self.entry = entry
|
||||
|
||||
def get_icon(self) -> str:
|
||||
# Return an icon based on the OS name
|
||||
if "arch" in self.name.lower():
|
||||
return "" # Arch Linux icon (using Font Awesome)
|
||||
elif "ubuntu" in self.name.lower():
|
||||
return "" # Ubuntu icon
|
||||
elif "windows" in self.name.lower():
|
||||
return "" # Windows icon
|
||||
else:
|
||||
return "" # Generic Linux icon
|
||||
|
||||
|
||||
def get_os_list() -> List[Entry]:
|
||||
entries_dir = "/boot/loader/entries/"
|
||||
entries = []
|
||||
|
||||
if path.exists(entries_dir):
|
||||
for entry_file in listdir(entries_dir):
|
||||
if entry_file.endswith(".conf"):
|
||||
with open(path.join(entries_dir, entry_file), 'r') as f:
|
||||
first_line = f.readline().strip()
|
||||
if first_line.startswith("title"):
|
||||
name = first_line.split(" ", 1)[1]
|
||||
entries.append(Entry(name, entry_file))
|
||||
return entries
|
||||
|
||||
|
||||
def set_boot_entry(entry: Entry):
|
||||
# Set the default boot entry using bootctl
|
||||
subprocess.run(["bootctl", "set-default", entry.entry], check=True)
|
||||
|
||||
|
||||
def reboot():
|
||||
# Reboot the system
|
||||
subprocess.run(["systemctl", "reboot"], check=True)
|
||||
0
src/main.py
Normal file
0
src/main.py
Normal file
5
src/style.css
Normal file
5
src/style.css
Normal file
|
|
@ -0,0 +1,5 @@
|
|||
|
||||
|
||||
.card {
|
||||
padding: 10px;
|
||||
}
|
||||
92
src/ui.py
Normal file
92
src/ui.py
Normal file
|
|
@ -0,0 +1,92 @@
|
|||
import os
|
||||
|
||||
import gi
|
||||
|
||||
gi.require_version("Gtk", "4.0")
|
||||
from gi.repository import Gtk, Gdk
|
||||
|
||||
from bootctl import get_os_list, set_boot_entry, reboot
|
||||
|
||||
|
||||
class CardListApp(Gtk.Application):
|
||||
def __init__(self):
|
||||
super().__init__(application_id="com.parchlinux.ParchBootManager")
|
||||
|
||||
def do_activate(self):
|
||||
# Create the main application window
|
||||
window = Gtk.ApplicationWindow(application=self)
|
||||
window.set_title("Parch Boot Manager")
|
||||
window.set_default_size(400, 400)
|
||||
|
||||
scrolled_window = Gtk.ScrolledWindow()
|
||||
scrolled_window.set_policy(Gtk.PolicyType.AUTOMATIC, Gtk.PolicyType.AUTOMATIC)
|
||||
window.set_child(scrolled_window)
|
||||
|
||||
# Create a vertical box to hold the cards
|
||||
card_list_box = Gtk.Box(orientation=Gtk.Orientation.VERTICAL, spacing=10)
|
||||
card_list_box.set_margin_top(10)
|
||||
card_list_box.set_margin_bottom(10)
|
||||
card_list_box.set_margin_start(10)
|
||||
card_list_box.set_margin_end(10)
|
||||
scrolled_window.set_child(card_list_box)
|
||||
|
||||
# Add multiple cards
|
||||
for entry in get_os_list():
|
||||
card = self.create_card(
|
||||
entry=entry,
|
||||
icon_name=entry.get_icon(),
|
||||
text=entry.name,
|
||||
button_label="boot",
|
||||
callback=self.on_card_button_clicked
|
||||
)
|
||||
card_list_box.append(card)
|
||||
|
||||
# Show the window
|
||||
window.present()
|
||||
|
||||
def create_card(self, entry, icon_name, text, button_label, callback):
|
||||
"""
|
||||
Create a card with an icon, text, and a button.
|
||||
"""
|
||||
# Create a container for the card
|
||||
card = Gtk.Box(orientation=Gtk.Orientation.HORIZONTAL, spacing=10)
|
||||
card.set_margin_top(5)
|
||||
card.set_margin_bottom(5)
|
||||
card.set_margin_start(5)
|
||||
card.set_margin_end(5)
|
||||
card.set_valign(Gtk.Align.START)
|
||||
card.add_css_class("card")
|
||||
|
||||
# Icon
|
||||
icon = Gtk.Image.new_from_icon_name(icon_name)
|
||||
icon.set_pixel_size(32) # Set icon size
|
||||
card.append(icon)
|
||||
|
||||
# Text
|
||||
label = Gtk.Label(label=text)
|
||||
label.set_xalign(0) # Align text to the left
|
||||
card.append(label)
|
||||
|
||||
# Button
|
||||
button = Gtk.Button(label=button_label)
|
||||
button.set_halign(Gtk.Align.START)
|
||||
button.connect("clicked", callback, entry) # Pass the card text as extra data
|
||||
card.append(button)
|
||||
|
||||
return card
|
||||
|
||||
def on_card_button_clicked(self, button, entry):
|
||||
set_boot_entry(entry.entry)
|
||||
reboot()
|
||||
|
||||
|
||||
css_provider = Gtk.CssProvider()
|
||||
css_file = os.path.dirname(os.path.abspath(__file__)) + '/style.css'
|
||||
css_provider.load_from_path(css_file)
|
||||
Gtk.StyleContext.add_provider_for_display(Gdk.Display.get_default(), css_provider,
|
||||
Gtk.STYLE_PROVIDER_PRIORITY_APPLICATION)
|
||||
|
||||
# Run the application
|
||||
if __name__ == "__main__":
|
||||
app = CardListApp()
|
||||
app.run()
|
||||
Loading…
Add table
Reference in a new issue