Written by varunjo the 27 Nov 09 at 07:13.

Just download the file, click on it , enter your password , Then it will ask you whether you want to install the software the repository contains.So simple.

Just download the file, click on it , enter your password , Then it will ask you whether you want to install the software the repository contains.So simple.

Written by Stebalien the 27 Nov 09 at 21:30.

Modify apt-url to support ppa links.
Ex:
normal apturl: apt:firefox
ppa apturl: ppa:user/ppa?install=firefox

Modify apt-url to support ppa links. Ex: normal apturl: apt:firefox ppa apturl: ppa:user/ppa?install=firefox

Written by yman the 30 Nov 09 at 02:38.

For example:
apt:w32codecs@packages.medibuntu.org

or something like that. If the repository isn't already included in sources.list, display a warning about installing software from untrusted sources.

EDIT:
Create a standard way for repositories to store their key, so it can be automatically retrieved when doing the above.

For example: apt:w32codecs@packages.medibuntu.org or something like that. If the repository isn't already included in sources.list, display a warning about installing software from untrusted sources. EDIT: Create a standard way for repositories to store their key, so it can be automatically retrieved when doing the above.

Written by snadrus the 1 Dec 09 at 22:11.

When installing google chrome, it adds the Google Labs repo to my system. This keeps things simple and is completely unnoticed except to experienced users. That way people can share DEBs (including out of date DEBs) and they will install fine & be updated later.

When installing google chrome, it adds the Google Labs repo to my system. This keeps things simple and is completely unnoticed except to experienced users. That way people can share DEBs (including out of date DEBs) and they will install fine & be updated later.

Written by mdhunn the 2 Dec 09 at 21:38.

I really like the idea of including the repo in the deb but security is a concern. being able to check keys against a certificate revocation list in launchpad and un-install software from a source would help. I know this would be a pain to implement but a centralized key and certificate server would help keep us from winding up like Windoze.

I really like the idea of including the repo in the deb but security is a concern. being able to check keys against a certificate revocation list in launchpad and un-install software from a source would help. I know this would be a pain to implement but a centralized key and certificate server would help keep us from winding up like Windoze.

Written by wolterh the 17 Dec 09 at 16:28.

This solution is pretty much the same as Solution #1, but with a small variation.

A button should be placed in the site to install the package, another to download. If one clicks the download button, solution #1 pretty much describes what should happen. If one clicks on the install button, this is what will happen:
1. User gets prompted for password (gksu style)
2. EULA-style dialog appears asking the user if he/she approves the provider's gpg key.
3. GUI opens up (maybe Ubuntu Software Center*) downloading the package for later installation. The package is downloaded where packages are usually downloaded when one installs via [apt-get install].

---
*If Ubuntu Software Center is used, then there must be an indication that the package is not in the official repository (universe or whatever). Maybe the tabs could be re-arranged, in the following way:
-Official Repository
-Third-Party Repositories
---------------------
-Installed Software

This solution is pretty much the same as Solution #1, but with a small variation. A button should be placed in the site to install the package, another to download. If one clicks the download button, solution #1 pretty much describes what should happen. If one clicks on the install button, this is what will happen: 1. User gets prompted for password (gksu style) 2. EULA-style dialog appears asking the user if he/she approves the provider's gpg key. 3. GUI opens up (maybe Ubuntu Software Center*) downloading the package for later installation. The package is downloaded where packages are usually downloaded when one installs via [apt-get install]. --- *If Ubuntu Software Center is used, then there must be an indication that the package is not in the official repository (universe or whatever). Maybe the tabs could be re-arranged, in the following way: -Official Repository -Third-Party Repositories --------------------- -Installed Software

Written by Ssdg the 2 Jan 10 at 15:12.

Relying on a 3rd party repository means relying on it's manager for the very stability and safety of your system. because package installation allows full access to the core of your system (kernel, network, filesystems, MBR,...) and to replace already installed packages (including libraries. I might be a good thing, or not.)

Everytime a new repository is set, you allow a new organisation/person to gain this access.

Those facts should be stated to the user in order for him to take the right decision.

Relying on a 3rd party repository means relying on it's manager for the very stability and safety of your system. because package installation allows full access to the core of your system (kernel, network, filesystems, MBR,...) and to replace already installed packages (including libraries. I might be a good thing, or not.) Everytime a new repository is set, you allow a new organisation/person to gain this access. Those facts should be stated to the user in order for him to take the right decision.

Written by TwistedLincoln the 5 Jan 10 at 19:34.

It's already possible for 3rd party vendors to create .deb files that add their repo info and GPG key. We should just encourage this rather than design a new system.

It's already possible for 3rd party vendors to create .deb files that add their repo info and GPG key. We should just encourage this rather than design a new system.

Written by Clorox the 9 Jan 10 at 05:50.

Currently, the feature is there, but the developers don't want to enable it because of security reasons. If it were enabled, then repositories could be added easily "with one click".

Currently, the feature is there, but the developers don't want to enable it because of security reasons. If it were enabled, then repositories could be added easily "with one click".

Written by undecim the 11 Jan 10 at 03:44.

In addition to solution #1, the user should have the option of installing only selected package(s) from a repository.

This allows the user to install an application without providing the maintainer continued access to the user's system, and also keeps the user safe should the repository become compromised later.

This also allows a package to be installed if a repository causes a dependency paradox, but the desired package(s) do not.

In addition to solution #1, the user should have the option of installing only selected package(s) from a repository. This allows the user to install an application without providing the maintainer continued access to the user's system, and also keeps the user safe should the repository become compromised later. This also allows a package to be installed if a repository causes a dependency paradox, but the desired package(s) do not.

Written by pluto4ps the 13 Dec 09 at 09:08.

So What I say is Ubuntu Software Centre should Add "System Requirements". Like ( Minimum RAM, Min Processor Speed, Min HDD Space, Min Graphics) etc.

So What I say is Ubuntu Software Centre should Add "System Requirements". Like ( Minimum RAM, Min Processor Speed, Min HDD Space, Min Graphics) etc.

Written by winerflo the 14 Dec 09 at 00:18.

In its metadata the program should have informations of what it needs to run : 1GO RAM / 500MO HDD space ...
Software center warns only when the computer doesn't reach the requirements.

Don't annoy us by displaying all these informations, let's the program manage it by itself.

In its metadata the program should have informations of what it needs to run : 1GO RAM / 500MO HDD space ... Software center warns only when the computer doesn't reach the requirements. Don't annoy us by displaying all these informations, let's the program manage it by itself.

Written by spocsterus the 28 May 10 at 01:51.

Each PC has different hardware and different software to drive that hardware. the benchmarking system in ubuntu should be able to give this combination a number rating, which then could be used by a seperate gaming browser as to whether a game will work and what requirements to make it work.

Each PC has different hardware and different software to drive that hardware. the benchmarking system in ubuntu should be able to give this combination a number rating, which then could be used by a seperate gaming browser as to whether a game will work and what requirements to make it work.