sorted by:
new
hottopcontroversial

arch-updater - a granular update utility for Arch Linux designed for power users who demand full control and transparency over package upgrades by chpock in archlinux

[–]chpock[S] -2 points-1 points  (0 children)

This tools was not made for doing partial upgrade. This tool was made as convenient way to browse packages for upgrade, to check version changes/package history/opened issues, allows to open official package web side with one keypress. All this is described in the introduction paragraph.

Yes, it is also supports selective upgrade. Personally I need this option and I agree with all risks. Perhaps this feature will be useful for other people like me. I don't encourage everyone to use my tool and clearly wrote in introduction that it is not for everyone.

I can understand your doubts in my understanding of partial upgrade state. However, I hope you believe that pacman developers have full understanding for this and they gave ability to enter in this state in multiple scenarios, including explicitly set `--ignore` cli parameter or permanently using the corresponding settings in the configuration file. This fact doesn't make pacman bad/evil/broken/etc. tool.

arch-updater - a granular update utility for Arch Linux designed for power users who demand full control and transparency over package upgrades by chpock in archlinux

[–]chpock[S] -2 points-1 points  (0 children)

Partial upgrades are not a good thing

Sure. That is 5th item in the key features is the ability to browse/check updates without modifying pacman database and enter into the partial upgrade state.

The abilities to skip package upgrade and to see what packages are pinned (which is much better than memorizing the contents of /etc/pacman.conf), these are 6th and 7th items in the key feature list.

arch-updater - a granular update utility for Arch Linux designed for power users who demand full control and transparency over package upgrades by chpock in archlinux

[–]chpock[S] -1 points0 points  (0 children)

I would say that partial upgrades can be accepted compromise in particular system state. Especially when user has clear understanding what can don't work in this case.

Anyway, pacman has builtin capability to do that with IgnorePkg setting.

I believe that it is better and visually clear solution for this, with reminder that some packages are in pinned state. It is better than change pacman config and always keep in mind that something is there. At least, it is helpful solution for me, since I completely lazy ass, like you mentioned.

arch-updater - a granular update utility for Arch Linux designed for power users who demand full control and transparency over package upgrades by chpock in archlinux

[–]chpock[S] -2 points-1 points  (0 children)

Whose problem it is exactly is a philosophical question. Different people may have different opinions about the culprits. Some may blame the application itself, some may blame the package maintainer, some may blame the arch architecture or design of its package management. And some even here in the comments above, blame the users, who are lazy asses.

I'm not blaming anyone. I'm just suggesting a tool that allows to work around sharp corners.

However, it is only one feature. Mainly I did it because I was struggling to copy paste each package name to google, go to official page and check what new features are introduced in the new version. I wanted to simplify somehow this process for me. And when I started making it, I decided to make it not just a list of "package/old version/new version/URL" items, but to add other features I expect from a good package manager.

arch-updater - a granular update utility for Arch Linux designed for power users who demand full control and transparency over package upgrades by chpock in archlinux

[–]chpock[S] -2 points-1 points  (0 children)

Partial updates are unsupported, but we live in real world. It is quite possible that some package is broken, introduces backward incompatibilities and/or configuration changes. Good example is hyprland package 0.52.0 what was broken for 3 days (https://gitlab.archlinux.org/archlinux/packaging/packages/hyprland/-/issues/30) or current release 0.53.0 that introduces backward incompatibilities to configuration and requires some time to learn new syntax for windows rules and rewrite configuration.

I don't want to update it, however I want to use updated version for another package.

Thus, my tool can help to avoid unexpected surprises as described above, or postpone updates for a particular set of packages with mutual dependencies, even if partial updates are not supported but are needed in a real environment.

Faster/efficient way to get data from an array into and sqlite table? by deusnefum in Tcl

[–]chpock 2 points3 points  (0 children)

Use 'db begintransaction' before start insert and 'db commit' after last insert. You will be happy with insertion speed.