Open AlphaNERD- opened 4 months ago
At the moment setup is heavily WIP, so detect.sh
won't cause any problems.
I'll have to have a play around with MX Linux when I get a chance, if you just force distid.sh
to report the correct package type everything should work from there. :thinking:
Hello there,
i‘ve ran into an issue while compiling the transformation pack: When i use chkdeps.sh to list the missing dependencies, i get a list of packages i cannot obtain using my package manager.
Through some diagnosis i found out that distid.sh is misidentifying my MX Linux installation for Red Hat. That is because MX Linux also has rpm installed and distid.sh solely looks for package managers when identifying OSes. That and rpm is checked before apt.
I forked the repo to implement a workaround in distid.sh (basically look for a distid.txt and take that to identify the distro). However i could still run into problems down the line depending on if and how setup.sh is used. I didn‘t implement my workaround into detect.sh and i wouldn‘t be surprised if that‘s why i can‘t fully apply the theming.