You are not logged in.
Pages: 1
I highly recommend making tazpkg capable of this as I've had to restore my system numerous times from the lack of this
Notice in the attachment how pacman doesn't continue if it'll break the listed deps ([c]required by ________[/c])
tazpkg on the other hand doesn't tell you of any broken deps until after you remove
(even more annoying, there's a timeout which cancels the rest of the operation, so you don't even know everything broken if you're verifying something)
[attachment=53665,3792]
Offline
Also notice how I can specify multiple packages for removal 
That's another improvement I'd like to suggest as well 
Offline
All on SliTaz follow Keep it simple philosophy, not all feature implemented.
Yes good suggest, multiple packages installation/removal not implemented, think need to add it on my todo.
I always implement those features in tazpkg on '6.0' :
- check if tazpkg need to be upgrade before install package or upgrade all packages
- fetch all packages in one transaction before install them instead fetch/install each sequentially
Offline
HAH, dw, I won't suggest anything that's too overly complicated 
All you gotta do is scan the installed dependencies
which you already have implemented on a similar level to pacman in [c]/var/lib/tazpkg/installed/<package>/recipt[/c] -> [c]DEPENDS=""[/c]
for comparison, pacman uses [c]/var/lib/pacman/local/libtasn1-4.18.0-1/desc[/c] -> [c]%DEPENDS%\nglibc\n[/c] to display those errors if I were to remove glibc
it just queries everything before actually running
not that hard to implement 
(if you're curious, I'm sort of building my own package manager that builds Appimages out of other package manager implementations, and everything except dpkg is simple to follow (heck it can even downlo0ad from other repo archives), unless you count the stuff like snap or flatpak, but like everything else I'm building, it's still a WIP project) 
Offline
Pages: 1
[ Generated in 0.026 seconds, 8 queries executed - Memory usage: 1.54 MiB (Peak: 1.77 MiB) ]