dpkg vs apt

273 · 12-02-2016, 02:10 PM

Quote:

Originally Posted by Habitual

We get google chrome from .deb and it updates itself most regularly.....

when the Chrome .deb is installed one of the things it does is add a repository to your system -- remove that repository and it will not longer update.
A few package do that but, to my mind, it's almost worse that they do because they're altering a system file when all you want is a browser. Yes it's convenient but, to me at least, it almost seems sneaky -- I'd rather Google publish repositories as Oracle do for VirtualBox, for example. But that's just my opinion.

replica9000 · 12-02-2016, 05:05 PM

Quote:

Originally Posted by 273

when the Chrome .deb is installed one of the things it does is add a repository to your system -- remove that repository and it will not longer update.
A few package do that but, to my mind, it's almost worse that they do because they're altering a system file when all you want is a browser. Yes it's convenient but, to me at least, it almost seems sneaky -- I'd rather Google publish repositories as Oracle do for VirtualBox, for example. But that's just my opinion.

They used to publish the repo on their website some time ago, which is where I originally got Chrome from. I also agree that the package shouldn't add it's own source entry either. Seems like M$ behavior to me.

rokytnji · 12-03-2016, 01:03 PM

Opera also asks if you want to add their repository to your sources list when you download and install their .deb file.

At least that was so last time I tried Opera.

Code:

deb http://deb.opera.com/opera/ stable non-free

273 · 12-03-2016, 02:08 PM

Quote:

Originally Posted by rokytnji

Opera also asks if you want to add their repository to your sources list when you download and install their .deb file.

At least that was so last time I tried Opera.

Code:

deb http://deb.opera.com/opera/ stable non-free

Ah, I thought Opera was different but forgot how. It asks, which is a good middle-ground if you ask me.