Screenfetch logo
is just the hooks has no owner, and pacman is strict on it…most problem comes probably if there is a online install. Read full topic
View ArticleScreenfetch logo
True, we need to change the installer not to install those hooks from outside the new endeavouros-theming package. @fernandomaroto @joekamprad Read full topic
View ArticleScreenfetch logo
the update like this can be fixed with --overwrite=’/blabla/*’ as example, but in installation you have no choice (installer) Read full topic
View ArticleScreenfetch logo
Am I the only one who thinks it is somewhat odd to have those hooks in the EOS theming package? If someone thinks “hey, i don’t use the EOS themes so I am going to remove that package”, their machine...
View ArticleScreenfetch logo
personal opinion, such configuration you could say endeavour-core, basicly you also theming at the end Read full topic
View ArticleScreenfetch logo
package name is a bit misleading sure, as it is more eos basic files and config. And we do not thinking till the end for the change with the hooks. Read full topic
View ArticleScreenfetch logo
Some great insights for a learner here. Thanks! Wondered if there was a way to look at my whole endeavouros system and work out which files aren’t owned by a pacman package. After all, apart from...
View ArticleScreenfetch logo
ososos: some are configuration, if you put those in a package and Dev X change a setting, is only bad for the enduser on some point if your system changed to finish mayby update-mirrorlist is other...
View ArticleScreenfetch logo
What’s the best way to get a full recursive list, including false positives, as the technique used only goes one level down? Is update-mirrorlist part of the welcome? Read full topic
View ArticleScreenfetch logo
ososos: update-mirrorlist It is part of the EndeavourOS installer only. Read full topic
View ArticleScreenfetch logo
ososos: What’s the best way to get a full recursive list, including false positives, as the technique used only goes one level down? I am not sure how useful of an effort that is because there will be...
View ArticleScreenfetch logo
Thanks! Another first with comm. There are a lot of false positives! But, great for learning. Used a grep to control the output for lines starting ^/bin. Brilliant! Read full topic
View ArticleScreenfetch logo
ososos: Used a grep to control the output for lines starting ^/bin. You could also change the find command to limit the results. For example, this would limit the results to just /bin comm -13...
View ArticleScreenfetch logo
ososos: error: No package owns /bin/pacstrap_calamares error: No package owns /bin/update-mirrorlist Mmmm. Just realised there’s a discepancy between the comm output for /bin which shows nothing, and...
View ArticleScreenfetch logo
dalto: comm -13 <(pacman -Qlq $(pacman -Qq) | sort) <(sudo find /bin -type f | sort) It is because I am excluding symbolic links and /bin is really a just a link to /usr/bin What happens if you...
View ArticleScreenfetch logo
ososos: Wondered if there was a way to look at my whole endeavouros system and work out which files aren’t owned by a pacman package. You can also use pacreport utility from pacutils package (a very...
View ArticleScreenfetch logo
Tasia91: sudo pacreport --unowned-files That certainly seems more useful. It does seem to filter out some paths by default though. Read full topic
View ArticleScreenfetch logo
dalto: It does seem to filter out some paths by default though. Man says there’s a config where that can be specified… Read full topic
View Article
More Pages to Explore .....