Written by adn the 3 Oct 09 at 06:35.

Change drives Shell deb, and upload them to hardware controllers

Change drives Shell deb, and upload them to hardware controllers

Written by ubunteando the 31 Jul 08 at 08:47.

Create a new way to handle "links" from webs that:

- Automatically add a repository to your sources file.
- Installs the program (erasing previous versions of it.
- Prompts you with a "enter password" GUI, but doesn't open terminal.

Why:
- No need to use terminal which annoys/draws back users.
- Would be able to easily update programs not waiting until the next release of Ubuntu (Transmission, Banshee...)
- Would reduce bandwidth load of official repositories.
- Wouldn't reduce effort to keep central repositories up-to-date (actually this process tends to be slow for non "flagship" programs)

e.g.:
1)I go to banshee download site
2)I click on the Ubuntu version button
3)It prompts me with a GUI to input user password, and tells me if im sure of the source im downloading from.
4)It adds automatically banshee repository, apt-get update, install, replaces old versions...
5)From now on my program depends of banshee's team development process and not ubuntu.

Create a new way to handle "links" from webs that: - Automatically add a repository to your sources file. - Installs the program (erasing previous versions of it. - Prompts you with a "enter password" GUI, but doesn't open terminal. Why: - No need to use terminal which annoys/draws back users. - Would be able to easily update programs not waiting until the next release of Ubuntu (Transmission, Banshee...) - Would reduce bandwidth load of official repositories. - Wouldn't reduce effort to keep central repositories up-to-date (actually this process tends to be slow for non "flagship" programs) e.g.: 1)I go to banshee download site 2)I click on the Ubuntu version button 3)It prompts me with a GUI to input user password, and tells me if im sure of the source im downloading from. 4)It adds automatically banshee repository, apt-get update, install, replaces old versions... 5)From now on my program depends of banshee's team development process and not ubuntu.

Written by yman the 10 Sep 08 at 03:52.

I would like to have something like "allsources.list", which lists all the sources for all packages that were installed on the system. It will also list the permissions attributed to each repository, which are:
* Allow installation of new packages from this repository?
* Allow this repository to update it's own packages?
* Allow this repository to update other repository's packages?
* Allow other repositories to update this repository's packages?
* Does this repository "steal" ownership of packages it updates? (for instance, if I installed Glest from getdeb and Glest later gets updated by Ubuntu universe, should getdeb remain the owner, thus allowing it to continue updating Glest, or should Ubuntu universe become the new owner?)
* Prevent other repositories from stealing ownership of this repositories packages?

allsources.list will also list the default configuration for new sources, which applies even before any packages are installed. This means that if the default configuration forbids new installs, then no packages of new sources can be installed.

I would like to have something like "allsources.list", which lists all the sources for all packages that were installed on the system. It will also list the permissions attributed to each repository, which are: * Allow installation of new packages from this repository? * Allow this repository to update it's own packages? * Allow this repository to update other repository's packages? * Allow other repositories to update this repository's packages? * Does this repository "steal" ownership of packages it updates? (for instance, if I installed Glest from getdeb and Glest later gets updated by Ubuntu universe, should getdeb remain the owner, thus allowing it to continue updating Glest, or should Ubuntu universe become the new owner?) * Prevent other repositories from stealing ownership of this repositories packages? allsources.list will also list the default configuration for new sources, which applies even before any packages are installed. This means that if the default configuration forbids new installs, then no packages of new sources can be installed.

Written by nloewen the 3 Jun 09 at 23:52.

see http://blog.nixternal.com/2009.06.01/my-thoughts-about-apt-url/

Note his reasons for using apt-url.
* The package isn’t available in Ubuntu?
* The package is outdated in Ubuntu?
* The package is broken in Ubuntu?
shouldn't we be working on these problems instead?

Another good point made,
"If these people running these repos can contribute to their own repo, why can’t they contribute to ours? Shouldn’t we be trying to recruit these people? Shouldn’t we be trying to hold on to the ones we have now?"

Seems a lot better than a possible insecure (although convenient) apt-url.

see http://blog.nixternal.com/2009.06.01/my-thoughts-about-apt-url/ Note his reasons for using apt-url. * The package isn’t available in Ubuntu? * The package is outdated in Ubuntu? * The package is broken in Ubuntu? shouldn't we be working on these problems instead? Another good point made, "If these people running these repos can contribute to their own repo, why can’t they contribute to ours? Shouldn’t we be trying to recruit these people? Shouldn’t we be trying to hold on to the ones we have now?" Seems a lot better than a possible insecure (although convenient) apt-url.

Written by nloewen the 4 Jun 09 at 00:02.

This is probably more of what ubunteando was going for when he posted this.

see http://doctormo.wordpress.com/2009/06/01/ubuntu-apt-url-and-the-white-list/
(in the article trust refers to I trust this person is who they say they are and confidence is I trust this person is able to code software that won't screw my computer over)

I like how he has the system of trust set up although it would be nice if it also had a way of communicating confidence in the software as well.

This is probably more of what ubunteando was going for when he posted this. see http://doctormo.wordpress.com/2009/06/01/ubuntu-apt-url-and-the-white-list/ (in the article trust refers to I trust this person is who they say they are and confidence is I trust this person is able to code software that won't screw my computer over) I like how he has the system of trust set up although it would be nice if it also had a way of communicating confidence in the software as well.

Written by Clorox the 13 Aug 09 at 06:58.

Go ahead and type "man apturl" in a terminal. It plainly says that the functionality already exists, but it is disabled currently due to security concerns (you can add just about any repository by a single click, including malicious repositories). But if the "trust" system in the blog post or a whitelist is implemented, then the feature could be enabled.

Go ahead and type "man apturl" in a terminal. It plainly says that the functionality already exists, but it is disabled currently due to security concerns (you can add just about any repository by a single click, including malicious repositories). But if the "trust" system in the blog post or a whitelist is implemented, then the feature could be enabled.