Contributor Stalker72 on Synaptic package manager
Easy package instalation for non-admins
Written by josinalvo the 11 Nov 08 at 19:30.
New
The idea is to have a daemon to allow package instalation by users that do not have admin privileges. ONLY PACKAGES FROM WHITELISTS ( these whitelists would include only packages from official repositories, and amongst them only those that are not security problems) WOULD BE AVAILABLE. users would not gain any admin priviledges. The system would be opt-in by the "guy with the sudo".
I say that as a sysadm myself: there are many trivial packages that a user should be able to install, like games, browsers, WMs, msn clones, educational tools, other shells ...
Not only this is nice if the user launches the instalation himself, but it also allows programs to install other required programs on demand. On the Most Ideal of Worlds (tm) this could even replace some instances of "this program is not installed" from bash and other scripts
But isn't it madness ???
There can be restrictions both of which users (via a group or groups) and which packages (I'd say all users should be able to install amsn, but not all sshd. I think the easiest way to have such control would be to offer a few whitelists for the admin/sudoer to choose from, or alter if he wanted). There can also be a space limitation (per user, or global)
Users would not be given root. There would be a program that checks a file every now and then and installs packages that are there. Whenever the package requires root input or
is not authorised by default, the sysadmin/user with sudo would be notified. Surely, no user would be able to install a .deb that does not come from an ubuntu repository.
and, most importantly, this could be a package, stricly "opt-in" (or an easy opt-out) so that paranoid sysadmins don't take any chances.
Will help code if the idea is accepted !
Easier Software Source Adding
Written by Prominence the 14 Jan 09 at 22:45.
New
Alright, the concept of adding Software Channels to Ubuntu is great, and very innovative, but not very easy to do. So as an idea to simplify this, and also to take advantage of Ubuntu's easy and fast software installation. It's all in the idea solution really.
Solution #1:
Software Source Button
Ok, I realised that you could add Software sources and that'll support updates and add the place's software to the package manager, well, my idea is to get a button a website that is an Ubuntu supporter and has software for the OS.
So to add their stuff to the package manager and get them as a software resource, you click the button, and it'll add it to the Software Sources (maybe with the password entry for safety) and then it'll reload, and check for updates and whatnot.
It'll be simple, click the button, enter the password, that's it, and then you could go into Add/Remove or the Synaptic Package manager and get the software. Easy.
It'll be a complete new innovation, and also advertise Ubuntu.
Additional thought: Maybe once the software source is added, there could be a option to view the software that is available from the source.
Also will get rid of command lines, and some not-so-user friendly stuff. Also might want to look into a more Visual, Straight Forward Source manager.
Ok, I realised that you could add Software sources and that'll support updates and add the place's software to the package manager, well, my idea is to get a button a website that is an Ubuntu supporter and has software for the OS.
So to add their stuff to the package manager and get them as a software resource, you click the button, and it'll add it to the Software Sources (maybe with the password entry for safety) and then it'll reload, and check for updates and whatnot.
It'll be simple, click the button, enter the password, that's it, and then you could go into Add/Remove or the Synaptic Package manager and get the software. Easy.
It'll be a complete new innovation, and also advertise Ubuntu.
Additional thought: Maybe once the software source is added, there could be a option to view the software that is available from the source.
Also will get rid of command lines, and some not-so-user friendly stuff. Also might want to look into a more Visual, Straight Forward Source manager.
Solution #2:
Use Apturl
Written by
tgm4883 the 15 Jan 09 at 01:51.
Using Apturl, one could package their repo location in a file that would be placed at /etc/apt/sources.list.d/repo-name.list
This would make adding repos/PPA's easier as it would be a single click from a website, would require sudo priviledges, and would make the newly added repo removable via apt-get, synaptic, etc. This will automaticaly import the keys nessecery.
Using Apturl, one could package their repo location in a file that would be placed at /etc/apt/sources.list.d/repo-name.list
This would make adding repos/PPA's easier as it would be a single click from a website, would require sudo priviledges, and would make the newly added repo removable via apt-get, synaptic, etc. This will automaticaly import the keys nessecery.
Solution #3:
Use regular package files which will open with GDebi
Written by
Warbo the 15 Jan 09 at 07:55.
Packages can be linked to which add APT sources (determined automatically by the package's install scripts), GPG keys, etc. These will open with GDebi by default, whilst people without a browser/download client with apturl support can still access them and open with GDebi.
Fewer redundant protocols/implementations, more use of packages ;)
Packages can be linked to which add APT sources (determined automatically by the package's install scripts), GPG keys, etc. These will open with GDebi by default, whilst people without a browser/download client with apturl support can still access them and open with GDebi.
Fewer redundant protocols/implementations, more use of packages ;)
Solution #4:
take a look at fedora or opensuse
I think you should implement something similar to Fedora or openSuse, when you want to add a repository the system automatically import the keys.
I think you should implement something similar to Fedora or openSuse, when you want to add a repository the system automatically import the keys.
Solution #1:
Use the AND operator in quick search
Written by
carpex the 2 Apr 09 at 18:28.
Searching for "firefox plugin" should give you results that have the words firefox AND plugin.
Searching for "firefox plugin" should give you results that have the words firefox AND plugin.
Solution #2:
offer choice of AND and OR
Written by
waster the 2 Apr 09 at 19:44.
simple radio buttons
simple radio buttons
Solution #3:
Include Advanced search
For example, much like the one for the Google search engine, which would allow the user to specify certain criteria.
For example, much like the one for the Google search engine, which would allow the user to specify certain criteria.
Solution #4:
Use search queries.
Written by
Pizdec the 3 Apr 09 at 12:33.
Symbols &, |, ( and ) aren't using in package names. So, use them for defining search queries (and replace current OR for AND as in #1).
Symbols &, |, ( and ) aren't using in package names. So, use them for defining search queries (and replace current OR for AND as in #1).
Solution #6:
Like #3, using the standard descrption which is on development
There could be an advanced search in which we could choose in every parameter of the standardized description of packages given in idea 17929 solution#1 :
http://brainstorm.ubuntu.com/idea/17929/
Solution #7:
Use both AND and OR, but list by relevance
Written by
kareeser the 9 Apr 09 at 03:57.
That is... searching "firefox plugin" will list all of the items with both search terms in them, followed by items with only one or the other.
That is... searching "firefox plugin" will list all of the items with both search terms in them, followed by items with only one or the other.
Solution #8:
Add "Quick search options" to Settings -> Preferences
Quick Search has to be quick. Otherwise we have the traditional Search button.
So? We don't do anything to the main GUI, or else it won't be "simple" anymore.
Instead, we add an entry to Settings -> Preferences, under a new section called "Quick Search", and we have: ( [o] means a radio button.)
-----
Quick Search (in a little bigger font and bolded, just like other section titles in GTK+)
[o] Space between keywords means AND (in order)
(Example: searching for "epiphany web" brings up only packages that have, in its name/description, the two words in that exact order.)
[o] Space between keywords means AND (any)
(Example: searching for "epiphany web" brings up all packages that have the two words, regardless of the position of the two, in its name/description.)
[o] Space between keywords means AND and OR
(Example: searching for "epiphany web" brings up all packages that have the two words, together or separate, in that order or not, in its name/description (the package "firefox," though having no connection to the keyword "epiphany," will come up, because it just has the word "web" in its package description.)
Quick Search has to be quick. Otherwise we have the traditional Search button.
So? We don't do anything to the main GUI, or else it won't be "simple" anymore.
Instead, we add an entry to Settings -> Preferences, under a new section called "Quick Search", and we have: ( [o] means a radio button.)
-----
Quick Search (in a little bigger font and bolded, just like other section titles in GTK+)
[o] Space between keywords means AND (in order)
(Example: searching for "epiphany web" brings up only packages that have, in its name/description, the two words in that exact order.)
[o] Space between keywords means AND (any)
(Example: searching for "epiphany web" brings up all packages that have the two words, regardless of the position of the two, in its name/description.)
[o] Space between keywords means AND and OR
(Example: searching for "epiphany web" brings up all packages that have the two words, together or separate, in that order or not, in its name/description (the package "firefox," though having no connection to the keyword "epiphany," will come up, because it just has the word "web" in its package description.)
Adding a line in software source and instaling in 2 clicks
Written by MIlentije the 25 Aug 08 at 01:13.
New
I think installation of third party software can be more simple.
Now when you are installing a new third party software you must add a line in software source, then update, then you open synaptic or add/remove or terminal and search for the program or type a command.
Solution #1:
Adding a line in software soruce and instaling in 2 clicks
Suggestion is, while you are surfing the internet Ubuntu ppa lines change into install buttons. When you click (1`st click) it ask you: Do you wish to add new ppa line and install software? You click "Yes" (2`nd click), it automatically add a line, update and install new software.
This way of installation would be more comfortable and with better user experience.
Suggestion is, while you are surfing the internet Ubuntu ppa lines change into install buttons. When you click (1`st click) it ask you: Do you wish to add new ppa line and install software? You click "Yes" (2`nd click), it automatically add a line, update and install new software.
This way of installation would be more comfortable and with better user experience.
Solution #2:
Provide a GUI for adding PPA's
Written by
caish5 the 31 Aug 08 at 15:36.
Many software applications provide a PPA as the way to install the latest version to Ubuntu. At present you need to edit sources.list or go into the arcane synaptic app.
Many software applications provide a PPA as the way to install the latest version to Ubuntu. At present you need to edit sources.list or go into the arcane synaptic app.
Solution #3:
Use Apturl
Written by
Id2ndR the 15 Feb 09 at 16:59.
PPA's should be able to be added by apturl. Every PPA should automatically have a package that adds the PPA to your system, and also adds the key. This way adding a PPA to your system would be as simple as selecting which release you are using and clicking a link.
PPA's should be able to be added by apturl. Every PPA should automatically have a package that adds the PPA to your system, and also adds the key. This way adding a PPA to your system would be as simple as selecting which release you are using and clicking a link.
Solution #4:
use RUNZ
Written by
sf_007 the 15 Jun 09 at 02:09.
RUNZ allows the use of portable apps, therefore it makes it easy to deploy software, without the need to install. It should NOT replace APT, however, it would be a nice addition:
http://hacktolive.org/runz
RUNZ allows the use of portable apps, therefore it makes it easy to deploy software, without the need to install. It should NOT replace APT, however, it would be a nice addition:
http://hacktolive.org/runz
Solution #5:
Make 'deb' links autodetected in Firefox
Written by
oddeyed the 26 Jun 09 at 15:59.
Using greasemonkey, or another method, make it so that when a 'deb' link is detected, it will automatically become an apt url, and it can be simply clicked, and the 'Software Sources' program will open, go by itself to the 'Third Party Software' tab, and it will automatically add itself. This could be included in the 'Ubufox' Firefox addon.
Furthermore, when adding a program to the 'Software Sources' program, rather than just adding the 'deb' line, have a second box for a comment or description of the repository - for example 'Google Chromium daily builds'. This would be much better than what is the current situation; having to follow the deb line in the address box with a '#' and then insert the comment.
Using greasemonkey, or another method, make it so that when a 'deb' link is detected, it will automatically become an apt url, and it can be simply clicked, and the 'Software Sources' program will open, go by itself to the 'Third Party Software' tab, and it will automatically add itself. This could be included in the 'Ubufox' Firefox addon.
Furthermore, when adding a program to the 'Software Sources' program, rather than just adding the 'deb' line, have a second box for a comment or description of the repository - for example 'Google Chromium daily builds'. This would be much better than what is the current situation; having to follow the deb line in the address box with a '#' and then insert the comment.
Solution #6:
Make it a wizard.
Written by
onyxwolf the 8 Apr 10 at 17:17.
There is a GUI way currently; however, the GUI way to add new repositories can be confusing to new users (or non-CLI users). So difficult to understand that most developers who maintain their own repositories don't bother to give that way to add their repositories and the non-CLI user sees that you have to use CLI (some shutter at the word terminal, others will open terminal and freeze at the blinking underline at the initial prompt) and say nevermind, point me at the .exe (this is where you have to explain .deb). Currently the CLI is the easiest way... For example, Currently the CLI way to add the GLX-Dock (Cairo-Dock) Stable repository is
sudo -v
echo "deb
http://repository.glx-dock.org/ubuntu $(lsb_release -sc) cairo-dock ## Cairo-Dock-Stable" | sudo tee -a /etc/apt/sources.list
wget -q
http://repository.glx-dock.org/cairo-dock.gpg -O- | sudo apt-key add -
sudo apt-get update
While the current GUI way is to "enter in the complete APT line" which is "deb
http://repository.glx-dock.org/ubuntu karmic cairo-dock" but what new user knows that. They shouldn't have to google what an APT line is. Then, the repo authentication is completely separate, which it shouldn't be.
The wizard could be one that can ask for each item per window, having some in a drop down type menu. The easiest and quickest way (and one that I think will be the easiest to implement for developers on their sites) will be a single text-table with multiple lines. That way they can use the same copy paste functionality as using CLI, but not as confusing or actually having to use terminal. Taking the example above...
1st Window-- New Other Software Source
Enter Software Source Information:
Source Type (text-table)deb (/text-table)
Source URL (text-table)
http://repository.glx-dock.org/ubuntu (/text-table)
Distribution (text-table)Karmic (/text-table)
Components (text-table)cairo-dock (/text-table)
Comments (text-table)Cairo-Dock-Stable (/text-table)
(Button)cancel(/Button) (Button)Add Source(/button)
2nd Window-- Authentication
Enter Key Information or Import Key:
Enter Key URL (text-box)
http://repository.glx-dock.org/cairo-dock.gpg (/text-box)
(Button)cancel(/Button) (Button)Get Key(/button) (Button)Import Local Keyfile(/Button) (Button)Skip Authentication(/button ## causes warning pop-up)
After they complete it, the wizard will auto create the APT-line and add it to sources.list without the end-user caring how that works, and apt-get will automatically update, then they can go to Software Center and get the wanted software.
Maybe even tie the two together, so you can hit a button from Software Sources that opens Software Center and it will show the packages from the newly added source.
So on GLX-Dock.org, the installation instructions will be...
To install--
Via GUI-- open System > Administration > Software Sources. Go to the Other Software Tab. Hit the add button. Copy the below and paste to the text box in the New Other Software Source window:
deb
http://repository.glx-dock.org/ubuntu
Karmic
cairo-dock
Cairo-Dock-Stable
Then in the Authentication Window enter in:
http://repository.glx-dock.org/cairo-dock.gpg
Then hit the "Get Key" button. Then open Software Center and install GLX-Dock!!!
There is a GUI way currently; however, the GUI way to add new repositories can be confusing to new users (or non-CLI users). So difficult to understand that most developers who maintain their own repositories don't bother to give that way to add their repositories and the non-CLI user sees that you have to use CLI (some shutter at the word terminal, others will open terminal and freeze at the blinking underline at the initial prompt) and say nevermind, point me at the .exe (this is where you have to explain .deb). Currently the CLI is the easiest way... For example, Currently the CLI way to add the GLX-Dock (Cairo-Dock) Stable repository is
sudo -v
echo "deb http://repository.glx-dock.org/ubuntu $(lsb_release -sc) cairo-dock ## Cairo-Dock-Stable" | sudo tee -a /etc/apt/sources.list
wget -q http://repository.glx-dock.org/cairo-dock.gpg -O- | sudo apt-key add -
sudo apt-get update
While the current GUI way is to "enter in the complete APT line" which is "deb http://repository.glx-dock.org/ubuntu karmic cairo-dock" but what new user knows that. They shouldn't have to google what an APT line is. Then, the repo authentication is completely separate, which it shouldn't be.
The wizard could be one that can ask for each item per window, having some in a drop down type menu. The easiest and quickest way (and one that I think will be the easiest to implement for developers on their sites) will be a single text-table with multiple lines. That way they can use the same copy paste functionality as using CLI, but not as confusing or actually having to use terminal. Taking the example above...
1st Window-- New Other Software Source
Enter Software Source Information:
Source Type (text-table)deb (/text-table)
Source URL (text-table)http://repository.glx-dock.org/ubuntu (/text-table)
Distribution (text-table)Karmic (/text-table)
Components (text-table)cairo-dock (/text-table)
Comments (text-table)Cairo-Dock-Stable (/text-table)
(Button)cancel(/Button) (Button)Add Source(/button)
2nd Window-- Authentication
Enter Key Information or Import Key:
Enter Key URL (text-box)http://repository.glx-dock.org/cairo-dock.gpg (/text-box)
(Button)cancel(/Button) (Button)Get Key(/button) (Button)Import Local Keyfile(/Button) (Button)Skip Authentication(/button ## causes warning pop-up)
After they complete it, the wizard will auto create the APT-line and add it to sources.list without the end-user caring how that works, and apt-get will automatically update, then they can go to Software Center and get the wanted software.
Maybe even tie the two together, so you can hit a button from Software Sources that opens Software Center and it will show the packages from the newly added source.
So on GLX-Dock.org, the installation instructions will be...
To install--
Via GUI-- open System > Administration > Software Sources. Go to the Other Software Tab. Hit the add button. Copy the below and paste to the text box in the New Other Software Source window:
deb
http://repository.glx-dock.org/ubuntu
Karmic
cairo-dock
Cairo-Dock-Stable
Then in the Authentication Window enter in:
http://repository.glx-dock.org/cairo-dock.gpg
Then hit the "Get Key" button. Then open Software Center and install GLX-Dock!!!
Solution #7:
Use a custom xml file similar to RSS
Written by
radel the 11 May 10 at 13:20.
With RSS we can subscribe to news feed, right?
Then with an hypothetical PPA we could subscribe to repository. It could be a simple XML file format with the classic ppa:foo/foo line and some other informations. Being a mime/type we can easily handle it, right?
Example:
In every PPA page just put a subscribe button, when you click on it it fires up ubuntu software center who can handle that PPA format and add the repo, simple as hell.
Also, software center could show "hottest" third party PPA (most subscribed) and things like that.
With RSS we can subscribe to news feed, right?
Then with an hypothetical PPA we could subscribe to repository. It could be a simple XML file format with the classic ppa:foo/foo line and some other informations. Being a mime/type we can easily handle it, right?
Example:
In every PPA page just put a subscribe button, when you click on it it fires up ubuntu software center who can handle that PPA format and add the repo, simple as hell.
Also, software center could show "hottest" third party PPA (most subscribed) and things like that.
Solution #8:
Add GUI in Package Manager for apt-add-repository ppa:
In Karmic, sudo apt-add-repository ppa: will add a PPA, with GPG key, to the sources list.
A GUI should be added to the options/software sources section of the package manager (KPackageKit in Kubuntu, and in Ubuntu, such that the user enters the PPA name in a text field, and the PPA is added using apt-add-repository (with appropriate PolicyKit configuration for the sudo command).
Something like:
PPA Name: [TEXT FIELD] ["Add PPA" button]
See example of apt-add-repository:
http://www.ubuntugeek.com/ubuntu-tip-simplified-way-to-add-ppa-repositories-in- karmic.html
In Karmic, <strong>sudo apt-add-repository ppa:<ppa name></strong> will add a PPA, with GPG key, to the sources list.
A GUI should be added to the options/software sources section of the package manager (KPackageKit in Kubuntu, and <whatever is used> in Ubuntu, such that the user enters the PPA name in a text field, and the PPA is added using apt-add-repository (with appropriate PolicyKit configuration for the sudo command).
Something like:
PPA Name: [TEXT FIELD] ["Add PPA" button]
See example of apt-add-repository:
http://www.ubuntugeek.com/ubuntu-tip-simplified-way-to-add-ppa-repositories-in-karmic.html
Solution #9:
Connect this procedure with Apparmor!
Written by
Lachu the 19 Nov 09 at 14:36.
The main reason, why we can't simple allow to automatically add additional repository is a security - newbie will add whatever repository to get installed few programs, either repository are untrusted.
User will be asked, he will install software/add repository, but additionally file contains repositories definition can contain category(connected to apparmor profile).
So dialog asking to add new repository could contains information:
"This action will add new repository to your system of games profile
Agree?
Yes|No"
I know, it's hard to realize, but this is only way. We need to integrate all software management tool to creating Apparmor profile of each installed program. It must also reads information about categorization.
In future we can prevent to game override files of system tool.
The main reason, why we can't simple allow to automatically add additional repository is a security - newbie will add whatever repository to get installed few programs, either repository are untrusted.
User will be asked, he will install software/add repository, but additionally file contains repositories definition can contain category(connected to apparmor profile).
So dialog asking to add new repository could contains information:
"This action will add new repository to your system of games profile
Agree?
Yes|No"
I know, it's hard to realize, but this is only way. We need to integrate all software management tool to creating Apparmor profile of each installed program. It must also reads information about categorization.
In future we can prevent to game override files of system tool.
Solution #10:
Import PPA Key from Launchpad in Software Sources
I would be nice if PPA keys were somehow automatically imported if the PPA is added. Alternatively an easy way to enter (for example) "B9F2A424372C883C411D917F5AFADBD4AA1C92B0" and have it import the gwibber-team PPA key, since that is the string listed on the PPA page.
I would be nice if PPA keys were somehow automatically imported if the PPA is added. Alternatively an easy way to enter (for example) "B9F2A424372C883C411D917F5AFADBD4AA1C92B0" and have it import the gwibber-team PPA key, since that is the string listed on the PPA page.
Solution #11:
user-keyring package
Written by
tgm4883 the 27 Jan 09 at 05:57.
The key should be automatically in a package on the users/teams PPA. Then, to add the key, all the user has to do is apt-get install user-keyring (obviously the user part would be replaced with the PPA owners name)
The key should be automatically in a package on the users/teams PPA. Then, to add the key, all the user has to do is apt-get install user-keyring (obviously the user part would be replaced with the PPA owners name)
Solution #12:
Provide a Key File for the user to import
Written by
Vadim P. the 28 Jan 09 at 18:17.
Right now, the user manually makes the key file and imports it.
Would be easier if there was an already-made key file they could just download and import.
Right now, the user manually makes the key file and imports it.
Would be easier if there was an already-made key file they could just download and import.
Solution #13:
gpgurl
Written by
medigeek the 25 Feb 09 at 20:08.
Basically solution #3 but with a slight change
There should be a link to use a gpg-url key, e.g. gpg://keyserver.ubuntu.com/B5140445
Which would get the server and the key to import it from.
Basically solution #3 but with a slight change
There should be a link to use a gpg-url key, e.g. gpg://keyserver.ubuntu.com/B5140445
Which would get the server and the key to import it from.
Solution #14:
Auto-generate a deb that imports the key and adds the PPA
Written by
fasaxc the 24 Aug 09 at 19:50.
The launchpad system could auto-generate a deb containing the key and the PPA link to add to sources.list. When installed, it would add the key and the source. The deb could be signed by ubuntu so that it can't be tampered with.
I'm thinking the deb would just be a download from the PPA site, not in the PPA or in the synaptic repository and would install via gDebi (for example).
This approach (or a similar one) is used by ubuntu-one.
The launchpad system could auto-generate a deb containing the key and the PPA link to add to sources.list. When installed, it would add the key and the source. The deb could be signed by ubuntu so that it can't be tampered with.
I'm thinking the deb would just be a download from the PPA site, not in the PPA or in the synaptic repository and would install via gDebi (for example).
This approach (or a similar one) is used by ubuntu-one.
Windows .exe to .bin Converter
Written by pjbmac the 17 Jan 09 at 00:55.
Not an idea
OK, we all know that the world is trying to run only windows *ack* Which means there are ALOT of .exe files out there that most everyone uses on a routine basis.
-41
votes
6
5
47
Solution #1:
Integrated .Exe to .Bin Converter
Written by
pjbmac the 17 Jan 09 at 00:55.
For those of us using various forms of Linux, why not find, integrate, or create a .exe to .bin converter. This will allow seemless integration from windows .exe to linux, but not the other way around.
For those of us using various forms of Linux, why not find, integrate, or create a .exe to .bin converter. This will allow seemless integration from windows .exe to linux, but not the other way around.
65
votes
66
6
1
Solution #2:
Continue to use (and improve) wine
Wine is an existing project to run .exe files in a Linux environment with no conversion necessary.
Wine is already available in the repositories.
Wine is an existing project to run .exe files in a Linux environment with no conversion necessary.
Wine is already available in the repositories.
-15
votes
1
4
16
Solution #3:
Merge solution #1 with Idea #15835
I guess that this idea could actually work with
Linux unified kernel . Which by the way isn't illegal or would cause Microsoft to sue us it's just an very strange idea.
If this would be implemented (yeah right), this should be an option not a default in anyway.
maybe stick it under the restricted exstras or something like that...
http://en.wikipedia.org/wiki/Linux_Unified_Kernel
For those that don't like links:
LUK imports all the key features of the Windows operating system kernel into the Linux kernel to support Windows applications and device drivers.
The article is a bit bias and it reads as propaganda, but if it's true and if implemented it would make Ubuntu a real counterpart to Windows.
Article claims that:
- Windows programs work without problem on LUK
- will work with hardware related native Windows dlls
- Windows driver framework will be implementable
I guess that this idea could actually work with <a href="http://brainstorm.ubuntu.com/idea/15835/" target="_blank">Linux unified kernel</a>. Which by the way isn't illegal or would cause Microsoft to sue us it's just an very strange idea.
If this would be implemented (yeah right), this should be an option not a default in anyway.
maybe stick it under the restricted exstras or something like that...
http://en.wikipedia.org/wiki/Linux_Unified_Kernel
For those that don't like links:
LUK imports all the key features of the Windows operating system kernel into the Linux kernel to support Windows applications and device drivers.
The article is a bit bias and it reads as propaganda, but if it's true and if implemented it would make Ubuntu a real counterpart to Windows.
Article claims that:
- Windows programs work without problem on LUK
- will work with hardware related native Windows dlls
- Windows driver framework will be implementable
0
votes
0
0
0
Solution #4:
Adaptive Driver Conversion
Written by
ct2193 the 8 Feb 10 at 17:48.
Proper driver support seems to be one of the biggest brick walls when it comes to other would-be Linux users.
I get that WINE allows you to run some Windows EXE files without recompilation. I also get that Linux implements device drivers in a different way from Windows, be it from need or just implementation. I have at least 2 directions this could go.
1) Implement a Linux-native support for Windows drivers. Not unlike how Windows Millennium supported both 9x drivers and NT drivers - only Linux stable.
2) Adaptively convert Windows Drivers for installed hardware into a Linux compatible installation. Possibly an interpreter that can make enough sense of the Windows INI files to script how a Linux hardware support backend responds to the hardware.
In this day and age, the inability to properly use modern hardware is just maddening. Let's face it, some of us really want to use Linux but the overhead of getting it to work on some hardware just sucks. Video, Audio and Network seem to be the main areas of complaint I see and more so in Audio and Video. Personally I scream when I find 1024x768 as my only possible resolution for my 28" Widescreen LCD.
Proper driver support seems to be one of the biggest brick walls when it comes to other would-be Linux users.
I get that WINE allows you to run some Windows EXE files without recompilation. I also get that Linux implements device drivers in a different way from Windows, be it from need or just implementation. I have at least 2 directions this could go.
1) Implement a Linux-native support for Windows drivers. Not unlike how Windows Millennium supported both 9x drivers and NT drivers - only Linux stable.
2) Adaptively convert Windows Drivers for installed hardware into a Linux compatible installation. Possibly an interpreter that can make enough sense of the Windows INI files to script how a Linux hardware support backend responds to the hardware.
In this day and age, the inability to properly use modern hardware is just maddening. Let's face it, some of us really want to use Linux but the overhead of getting it to work on some hardware just sucks. Video, Audio and Network seem to be the main areas of complaint I see and more so in Audio and Video. Personally I scream when I find 1024x768 as my only possible resolution for my 28" Widescreen LCD.
Hide main synaptic window when the installing dialog appears
Written by knopper67 the 18 Jan 09 at 01:57.
New
When I'm using synaptic package manager, all is fine until I press Apply.
The screen becomes cluttered with a useless, greyed out window in the background when I am installing packages. This VERY untidy and makes ubuntu feel unpolished.
This window is practically useless while your installing packages, so why is it there? To waste screen space and memory?
This behaviour is also present in the Update manager and the "Add/Remove Programs" Dialog.
Repositories are awkward to manage (manual adding/removing, keys, etc.)
Written by Warbo the 15 Jan 09 at 18:52.
New
The package manager is a great way of simplifying software management, but the initial hurdle of repositories can be awkward.
Repositories must be added and removed manually, requiring a separate package management tool to do so, manual adding of keys, there is an unneeded distinction between official repositories and third-party repositories, etc.
Simplifying this management, and removing as much redundancy as possible, would lower the barrier to entry considerably.
Solution #1:
Make packages for every repository
Written by
Warbo the 15 Jan 09 at 18:52.
Packages are very versatile things. They can contain files, like /etc/apt/sources.list.d/whatever, and scripts, which can write different values depending on the release they detect.
This means that packages can do everything needed to manage the APT sources, keys, etc. without needing a different (and currently manual) system. The current sources editor can be adapted to be a specialised package manager that only bothers with packages in a "Repository" category, whilst any package manager can be used to edit the repositories too. The main repository can be marked as an essential package (just like the apt package is) to prevent its removal.
With GDebi as the default tool to open packages with from Firefox, this also means that adding repositories from the Web is easy, since it is a simple download which opens in GDebi with an Install button.
Packages are very versatile things. They can contain files, like /etc/apt/sources.list.d/whatever, and scripts, which can write different values depending on the release they detect.
This means that packages can do everything needed to manage the APT sources, keys, etc. without needing a different (and currently manual) system. The current sources editor can be adapted to be a specialised package manager that only bothers with packages in a "Repository" category, whilst any package manager can be used to edit the repositories too. The main repository can be marked as an essential package (just like the apt package is) to prevent its removal.
With GDebi as the default tool to open packages with from Firefox, this also means that adding repositories from the Web is easy, since it is a simple download which opens in GDebi with an Install button.
Solution #2:
Handle the source.list with a GUI
Written by
Arnaudus the 15 Jan 09 at 19:59.
The interface does not need to be particularly complicated. One should access it from Synaptic (for instance, Edit -> Source List). The repositories of the source.list can be listed (say, on the left part of the window), when clicking on one of them, you should get more information about the repository (official or not, number of packages in it, status --on line, down, etc--). You can imagine to have a button to switch it on or off, a "Remove repository" button, and "Add repository" choice in which you just have to copy and paste the server name.
One of the reasons for that is the number of questions in the forum or in Launchpad about people who screwed up their source list trying to follow tutorials. Having a GUI would avoid all these problems --the worst thing that can happen is to misspell a server name, which has no effect except an error message.
[Edit]: Synaptic proposes an embryo for such a GUI, but it is more confusing than useful because different info are mixed up. I was referring to a GUI devoted to only one thing: editing the source list: one window, you see your source list, you click simple buttons to edit it. The current options are too far from the source list to be of any use for the beginner nor for the geek.
The interface does not need to be particularly complicated. One should access it from Synaptic (for instance, Edit -> Source List). The repositories of the source.list can be listed (say, on the left part of the window), when clicking on one of them, you should get more information about the repository (official or not, number of packages in it, status --on line, down, etc--). You can imagine to have a button to switch it on or off, a "Remove repository" button, and "Add repository" choice in which you just have to copy and paste the server name.
One of the reasons for that is the number of questions in the forum or in Launchpad about people who screwed up their source list trying to follow tutorials. Having a GUI would avoid all these problems --the worst thing that can happen is to misspell a server name, which has no effect except an error message.
[Edit]: Synaptic proposes an embryo for such a GUI, but it is more confusing than useful because different info are mixed up. I was referring to a GUI devoted to only one thing: editing the source list: one window, you see your source list, you click simple buttons to edit it. The current options are too far from the source list to be of any use for the beginner nor for the geek.
Solution #3:
Registry autodiscovery
Written by
qense the 15 Jan 09 at 20:20.
Create an autodiscovery specification for repositories that allows you to give a base URI to a repository after which, with help of the protocol, you can select the parts you want.
Care should be taken to not break the compatibility with the CLI.
An Avahi service could also be supported to support repositories inside networks, which should make life easier for sys-admins. A nice list of possible repositories could show up in the configuration dialogue.
Create an autodiscovery specification for repositories that allows you to give a base URI to a repository after which, with help of the protocol, you can select the parts you want.
Care should be taken to not break the compatibility with the CLI.
An Avahi service could also be supported to support repositories inside networks, which should make life easier for sys-admins. A nice list of possible repositories could show up in the configuration dialogue.
Solution #4:
Repository Index, Discovery and Trusted List
Written by
doctormo the 15 Jan 09 at 21:36.
Each apt repository currently operates via http, but has no way to search for packages or give you a list of other repositories that it needs to operate or that you may want to use to experiment with further updates.
I suggest that an index be created in the specification which can bind one repository to another or set of repositories as required. Sort of like repository dependency.
Each apt repository currently operates via http, but has no way to search for packages or give you a list of other repositories that it needs to operate or that you may want to use to experiment with further updates.
I suggest that an index be created in the specification which can bind one repository to another or set of repositories as required. Sort of like repository dependency.
Solution #5:
Extend AptUrl to to allow adding repositories by just clicking a link
Written by
Dim the 5 May 09 at 11:41.
Adding repositories is difficult. Here's the example, when you want to add Shutter's repository (it's a screenshot tool) you actually need to do lots of steps:
http://shutter-project.org/faq-help/ppa-installation-guide/. You can do this with our without terminal but either way are too complex.
We already have AptUrl (
https://wiki.ubuntu.com/AptUrl) to make it simple to install software from repositories by just clicking a link on a web page. Even websites like
http://appnr.com exist for that.
Wouldn't it be great to extent AptUrl to allow adding repositories by just clicking a link? So that Shutter and other software could just say on their websites: "Click here to add our repository". And then say, "After that, click here to install the program". Or even better, both: "Click here to add our repository and install the program".
Adding repositories is difficult. Here's the example, when you want to add Shutter's repository (it's a screenshot tool) you actually need to do lots of steps: http://shutter-project.org/faq-help/ppa-installation-guide/. You can do this with our without terminal but either way are too complex.
We already have AptUrl (https://wiki.ubuntu.com/AptUrl) to make it simple to install software from repositories by just clicking a link on a web page. Even websites like http://appnr.com exist for that.
Wouldn't it be great to extent AptUrl to allow adding repositories by just clicking a link? So that Shutter and other software could just say on their websites: "Click here to add our repository". And then say, "After that, click here to install the program". Or even better, both: "Click here to add our repository and install the program".
Solution #6:
Have a costum repository registered for each package
In ubuntu's default repos, some softwares may not be up-to-date (I don't blame anyone for that, it's a stability concern).
But what if I need to have, say, Wine to the most recent version? Gotta add the repository manually.
Why not instead have a custom repository registered for each package, in such a way that you can swich to the latest (but not officially supported) version of their soft with just a single right-click in the synaptic manager? Rather than using the 1.0.1 version aviable in the repos, I would now be synced with Wine's official PPA, recieving the updates as they come in to be always up to date, without editing any text-file!
In ubuntu's default repos, some softwares may not be up-to-date (I don't blame anyone for that, it's a stability concern).
But what if I need to have, say, Wine to the most recent version? Gotta add the repository manually.
Why not instead have a custom repository registered for each package, in such a way that you can swich to the latest (but not officially supported) version of their soft with just a single right-click in the synaptic manager? Rather than using the 1.0.1 version aviable in the repos, I would now be synced with Wine's official PPA, recieving the updates as they come in to be always up to date, without editing any text-file!
Add/Remove and Synaptic Have Overlapping Functionality and Poor User Interface
Written by linbai the 14 Jan 09 at 01:04.
New
[Updated 14Jan'09] Problem Statement: the PackageKit-based Add/Remove and Synaptic both use the same repository list, but use two completely different interfaces. One is easier to use, but offers fewer programs and functionality; the other offers more, but is only accessible who are highly familiar with Linux or spend a lot of time discovering precisely which combination of components to download. Why have two overlapping systems? It is confusing and unnecessary. Further, compared with many recent commercial solutions for unified software downloads, the UI on both solutions is terribly lacking. Even the comparatively straight forward Add/Remove UI (based on PackageKit) uses three different window panels to communicate information that could be done in one panel. Synaptic is worse. Compare this with the dead-simple download scheme for Apple's "App Store"/Google G1's "Market"/Palm Pre's TBA store. I remember Mark Shuttleworth saying in an interview years ago about the software download process being a unique user experience Linux offered unlike any other commercial solutions. Well, commercial solutions have caught up and passed Ubuntu on this front.
Solution #1:
Merge Front-end UI for Add/Remove and Synaptic -- Make UI More User Friendly
Written by
linbai the 14 Jan 09 at 01:04.
[Updated 14Jan'09] I believe a new front-end for how Synaptic and Add/Remove are displayed in Ubuntu should be designed, making it appear to users as if there is only one repository. There shouldn't be two parallel systems for beginner and advanced users. This new front-end should use a new, more user-friendly UI, where users can rate programs and leave comments. The UI should use only one single display and dialogue panel, use large icons when possible, and have a standard dummy when none is available. Also, the UI can have multiple views, just like Brainstorm does: i.e. most downloads, highest rated, newest first, oldest first, etc.
[Updated 14Jan'09] I believe a new front-end for how Synaptic and Add/Remove are displayed in Ubuntu should be designed, making it appear to users as if there is only one repository. There shouldn't be two parallel systems for beginner and advanced users. This new front-end should use a new, more user-friendly UI, where users can rate programs and leave comments. The UI should use only one single display and dialogue panel, use large icons when possible, and have a standard dummy when none is available. Also, the UI can have multiple views, just like Brainstorm does: i.e. most downloads, highest rated, newest first, oldest first, etc.
Solution #2:
Improve synaptic
Written by
eugene2k the 19 Jan 09 at 18:06.
In windows, when an application is installed the installer allows the user to choose some optional components, in linux we have to search the repository for those optional components. I suggest adding some functionality so that the user could get a simple list of main packages that can be installed or already are installed and then click a button in synaptic to choose to install or uninstall some of the optional components for a specific package. This would also make it possible to replace the current add/remove app.
In windows, when an application is installed the installer allows the user to choose some optional components, in linux we have to search the repository for those optional components. I suggest adding some functionality so that the user could get a simple list of main packages that can be installed or already are installed and then click a button in synaptic to choose to install or uninstall some of the optional components for a specific package. This would also make it possible to replace the current add/remove app.
Synaptic needs a way to follow updates in not in not-installed packages tooq
Written by ketilwaa the 7 Jan 09 at 21:31.
New
I like to keep my system to a minimum, so I don't install packages I don't really have no use for in their current form.
However, package X may be rumoured to have feature Y that I'm interested in, so I should be able to follow the history of that package even though it's not installed.
Also, I maintain two systems. System #1 is the one I use daily. I'd would like to know as soon as possible when there are updates that are very important for system #2. Like today, when there was an Nvidia update.
I propose a property tab that lists the package version history, like at which date it entered the repos, what package it superseded, etc.
Also, I'd like to see a config option that tells me packages X, Y, Z that are not installed on this system has updates, whenever I run the Synaptic equivalent of apt-get update