-
Notifications
You must be signed in to change notification settings - Fork 113
fixes issue https://github.com/rmarquis/pacaur/issues/681 #682
Conversation
This is a cheap workaround that doesn't fix the underlying issue. Not merging, but I suggest you keep it in a local branch while the main issue is being worked on. |
correct this does not solve the problem regarding IgnorePkg merge but it fixes the issue that one cannot choose a custom config file. so should I open a new issue that one cannot add a custom config file and point this PR to it? |
No, because as I pointed out, this is a workaround, not a fix. The underlying issue is tracked in #433. |
No what I wanted to say is: pacaur misses the option "--config" like pacman has. this has nothing to do with ignorepkg and is a complete other issue. |
@steadfasterX In the end, it is the same topic that it is shown in #433. I think it is better to find a complete solution and not workarounds for each issue derived from the same problem. |
Yes, exactly. Moreover, |
@ChuckDaniels87 @rmarquis
sorry I don't get u. the option --config is available for pacman so yes it should apply there as well. |
To do what, exactly? You're running around XY problem here. |
I share the PC with several users: me the full admin and "normal users" When I use pacaur i need complete different (therefore not merged) options for:
as the normal users would have. A normal user should be able to upgrade the system but e.g. not for the kernel. Example normal user conf (excerpt!):
Example admin user conf (excerpt!):
Each user will have an alias for pacaur pointing to |
So partial update? Hardly a valid user case, and in any case out of scope of the intended design. |
just an example. |
You just convinced me that letting some user handling packages and other only a subset of them is a crazy, stupid idea. Well, actually that's what I thought already, but you perfectly illustrated that your user case is not something pacaur should support. |
lol. so please remove it from pacman and yaourt as well ;) |
I think that config option can be implemented on
In any case, the user case that you suggested is totally unsupported on ArchLinux and strongly discouraged. The existence of config option is obviously not intended to be used on the user case you suggested. |
I know that partial upgrades are not supported. best example: Thunderbird + Lightning just a few days ago. Due to a change by mozilla to include lightning into thunderbird breaks the calendar completely on my system so I downgraded and set the package to ignore list. This is what I want to do for my "normal users". Partial Upgrades is the only way to solve issues like these and still keeping my system up2date.. Let's say that issue gets fixed in 3 weeks. that would mean to not get any update until then. Thats maybe ok for some but not for me. |
So, your users can break other users packages to workaround issues on their packages. If partial upgrade from system admin is unsupported and discouraged, letting "normal users" to upgrade, downgrade and ignore package at system level is a perfect recipe for disaster. You should look other solutions that support install packages on a per-user basis: flatpak, snap, appimage, spack, pip, etc. |
ok. then just tell me why IgnorePkg does exists? |
Just read the wiki, I've even put the link above for you.
I suggested you other proper package managers for your user case. Anyways, I think this is not the place to have a discussion about ArchLinux and Edit: sorry for polluting the thread. |
As said I know that article. But anyways. You have already made your decision - for your own reasons - to not include a valid option (--config) which exists in pacman. I just wanted to add a feature available in pacman for pacaur which I believe makes totally sense (and you not). story end. |
Could you please look into this? It works for me and was an easy fix for my problem..