Open Valeria-Fadeeva opened 8 months ago
eos_bootloader was never intended to be a general purpose module to be used by others. It was built to serve a very specific purpose so the current functionality is correct for that intended purpose.
That being said, I am not opposed to adding support for more package formats if it helps you. It would probably not come until after our upcoming release though.
only to mention.. this is only the fork of calamares we do use downstream for EndeavourOS, also stuff will may went into main calamares.. https://github.com/calamares/calamares
I have been developing my own distribution based on Arch Linux for 1.5 years. https://github.com/Melawy https://git.melawy.ru/explore/repos
The last problem was the installation.
Of all the distributions, I liked the installation approach from EndeavourOS.
I made a local fork and began to combine Calamares from 4 providers: Calamares original, EndeavourOS, CachyOS, KaOS.
And ArchISO configuration from EndeavourOS, CachyOS, XeroLinux, ArcoLinux.
Since I have packages for installing and designing rEFInd bootloader, I added it there.
Now I have the first Beta release and I am testing installation from disk and over the network in 3 options: rEFInd (with design), Systemd-boot, Grub2 (I also want with design).
I also want to make the rEFInd, Systemd-boot, Grub2 bootloaders create a boot menu based on the kernel located in (root)/EFI/Linux. And so that bootloaders, design and menus are on the EFI partition due to LUKS blocking.
I would be glad if my code could be added to your project and help others.
Thank you.
for other package archive
file: src/modules/eos_bootloader/main.py string:
replace:
example
to avoid pacman error - duplicate target (file.startswith(package + "-"))
to return list (for future checking data type)
before
after