On 09.05.2017 23:41, Erik Christiansen via luv-main wrote:
On 09.05.17 15:19, Michele Bert via luv-main wrote:
Anyway, there aren't any cons in installing a downloaded package
through dpkg, once you are sure it is safe. Of course the isn't any
automatic update of that package, but that's the only way to install a
third-party packaged not included in any repository.
I'm doing too many things at once here, and had missed the upthread
info
that the package had already been downloaded, so a simple dpkg install
from its current location is quick, easy, and a thing I've done in the
same circumstance, now that I'm synced with the whole thread.
Erik
_______________________________________________
luv-main mailing list
[email protected]
https://lists.luv.asn.au/cgi-bin/mailman/listinfo/luv-main
Debian's dpkg is a low level tool, its not automatic in any way, all
"dpkg -i somepackage.deb" will do is try to install the package named.
It will unpack the deb then look for any dependencies, if they are not
found its up to you to install them. When this is done running the same
command "dpkg -i somepackage.deb" will complete the task. If the package
fails to install, you CANNOT leave the system like that as the
incomplete install breaks Debians package management system. In this
case the package can be removed with "dpkg -r somepackage.deb" (leaves
the packages config files in place) or "dpkg --purge somepackage.deb"
(removes all the package).
While using dpkg is something of a pain, one can use it to get around
some of Debians strangeness's.
Lindsay
_______________________________________________
luv-main mailing list
[email protected]
https://lists.luv.asn.au/cgi-bin/mailman/listinfo/luv-main
