MX Linux Forum

newkansan wrote:...It's not clear to me what the difference is between installing a package from the MX Package Installer and installing it from Synaptic. I thought that maybe it was pulling from custom repos not available through Synaptic or was pulling extra packages in that aren't dependencies. I've tried installing Gnucash and Firefox and it seems that I could have installed these identically from Synaptic. ...

newkansan wrote:...After installing from MX Package Installer, when I re-enter the app, I expect the packages I installed to be checked (indicating they are already installed), but they are not. I think from a new user perspective, they might try to reinstall something that is already installed. ...

The main function of the MX Package Installer is to make it easier to install some of the more popular packages, but they could also be installed using Synaptic or from the command line using apt-get|aptitude|dpkg.

I'm not sure about having the currently installed packages "checked" when starting MX Package Installer, but do agree it would be nice to have some type of indication that a package is currently installed {maybe have a asterisk, or add another column to the show the current install status}

lucky9 wrote:I thought the whole idea of the MX/Meta Package Installer is to make it easier to install popular items. If you want to know if it's installed open Synaptic and use it's 'Installed Packages' and then it's Search function. (After all there's not many choices in the MX/Meta Package Installer. You really should know what you have done there.)

At any rate the use of Synaptic to find out if you installed something is pretty straightforward. There is a lot of information in the wiki on Synaptic. Enter Synaptic in the wiki search box to see what's available.

Utopia wrote:Colors can be misunderstood. Green looks like something that can be installed, but not in all parts of the world.
If the installed packages are invisible, there will be no questions like: "I want to install, but it's grayed out?".
Henry

Don't you think users will remember what they installed if reminded with grayed out in the listing?

Utopia wrote:Yes, but it doesn't say why they are unavailable.
Both alternatives that don't include color are fine with me.
Henry

Adrian wrote:Here's the last build please give it a try and let me know if you like the changes: https://github.com/AdrianTM/mx-packagei ... 1_i386.deb

A bit different issue, I've noticed that Opera doesn't install, I tried even from command line and I get this:

Code: Select all

Untrusted packages could compromise your system's security.
You should only proceed with the installation if you are certain that
this is what you want to do.

  opera 

Do you want to ignore this warning and proceed anyway?

Although I added opera security key... mx-packageinstaller also runs "wget -O - http://deb.opera.com/archive.key | apt-key add -"

Any ideas, suggestions?

For now, the "2013" key above is the one we use, but we may be switching to this one soon: ....

wget -qO- http://deb.opera.com/ | tac | grep BEGIN -B999 -m1 | tac | grep END -B999 | apt-key add -

root@mx1:/home/kent# wget -qO- http://deb.opera.com/ | tac | grep BEGIN -B999 -m1 | tac | grep END -B999 | apt-key add -
OK

root@mx1:/home/kent# apt-key list|grep -i opera -A2 -B2

pub 1024D/6A423791 2006-09-26 [expired: 2009-09-25]
uid Opera Software Archive Automatic Signing Key <hostmaster@opera.com>

pub 1024D/927CCC73 2007-06-04
--

pub 1024D/9D1A0061 2009-08-31 [expired: 2011-01-23]
uid Opera Software Archive Automatic Signing Key 2010 <packager@opera.com>

pub 1024D/B9FBE3CE 2011-01-22
--

pub 1024D/336064B5 2011-11-08 [expired: 2013-01-11]
uid Opera Software Archive Automatic Signing Key 2012 <packager@opera.com>

pub 1024D/09F8ECEF 2009-12-11
--

pub 4096R/A8492E35 2013-07-03 [expires: 2015-07-03]
uid Opera Software Archive Automatic Signing Key 2013b <packager@opera.com>
sub 4096R/08B288D5 2013-07-03 [expires: 2015-07-03]

root@mx1:/home/kent#