Multi-Download(NOT NSTALL) in ubuntu software center
Written by lophie the 22 Dec 09 at 17:50.
New
Hi all. I'll just get to the point.
The new ubuntu software centre is great but I noticed a great sit back. The USC is not "multi-installing" but it's multi queuing for installation which is a real time saver but still......
We know how hard to multi-install because of the lock and the deps and stuff and THAT IS NOT MY PROBLEM-IDEA HERE.
the problem is the queued software needs it's turn not only for installing but even for DOWNLOADING.
so why is this a problem? because when I fresh install or in need for multi programs I have to wait (for eg) netbeans to finish to install a MUCH smaller application.
Solution #2:
usc should download selected packages parallely like in previous ubuntu releases
Written by
bhuvi the 7 Jan 10 at 12:39.
in previous ubuntu versions like in ubuntu 9.04 when multiple packages are selected for install some of the packages would be downloaded in parallel when the internet connection is faster and would install them one by one.But ubuntu9.10 does not download the applications in parallel.This feature should be brought back to ubuntu.This coupled with ubuntu software centre's ability to select new apllications for install while previously selected one is downloading would make it more powerful
in previous ubuntu versions like in ubuntu 9.04 when multiple packages are selected for install some of the packages would be downloaded in parallel when the internet connection is faster and would install them one by one.But ubuntu9.10 does not download the applications in parallel.This feature should be brought back to ubuntu.This coupled with ubuntu software centre's ability to select new apllications for install while previously selected one is downloading would make it more powerful
Solution #3:
Stop and start
Written by
tommis the 18 Jan 10 at 17:43.
Provide an option to stop downloading and continue it when ever you are ready.
Provide an option to stop downloading and continue it when ever you are ready.
Solution #4:
choose number of downloads
i think USC should also have an option to control the number of downloads
i think USC should also have an option to control the number of downloads
Solution #5:
"Add to List" Option in USC
Put an "Add to List" right next to the install button currently in USC, and make an additional button (possibly near the search box) that's labeled something to the extent of "Install List of selected programs"
Also, on the left sidebar, make an entry for selected (but not yet installed) packages, similar to the Get Software and Installed Software entries.
It'll act a bit like the old gnome-app-install...and the new USC, all at the same time.
Put an "Add to List" right next to the install button currently in USC, and make an additional button (possibly near the search box) that's labeled something to the extent of "Install List of selected programs"
Also, on the left sidebar, make an entry for selected (but not yet installed) packages, similar to the Get Software and Installed Software entries.
It'll act a bit like the old gnome-app-install...and the new USC, all at the same time.
Make launchpad package installation simple.
Written by varunjo the 27 Nov 09 at 07:13.
New
Right now , for installing anything from launchpad, we have to open software sources, add the repository, and the install the package. This should be made easy.
Solution #1:
Make a simple .rep extension which contains the deb line and the gpg key.
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.
Solution #2:
Use apt-url
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
Solution #3:
Modify apt-url to support 3rd party repositories
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.
Solution #4:
Include repo in deb (Google Chrome does this)
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.
Solution #5:
Include the repo and use rsa type keys and certificates
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.
Solution #6:
.rep package + optional install-on-the-spot button on website
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
Solution #7:
And never forgot to show the appropriate warning.
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.
Solution #8:
Use Deb packages instead
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.
Solution #9:
AptURL can already do this - get developers to enable it
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".
Solution #10:
And provide the option to install only select package(s) from a repository
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.