December 2009 - openSUSE Features - openSUSE Mailing Lists

[New: openFATE 308324] location-based ornting
by fate_noreply＠suse.de 16 Aug '11

16 Aug '11

Feature added by: Anar Taori (anartaori) Feature #308324, revision 1 Title: location-based ornting openSUSE-11.3: Unconfirmed Priority Requester: Mandatory Requested by: Anar Taori (anartaori) Partner organization: openSUSE.org Description: ability to print to nearest printer based on client device connecting in from Test Case: xyz Use Case: healthcare - doctor enters patient room .... Business case (Partner benefit): openSUSE.org: benefit - hipaa compliance -- openSUSE Feature: https://features.opensuse.org/308324

1 2

[openFATE 308045] Switch to native printer config
by fate_noreply＠suse.de 16 Aug '11

16 Aug '11

Feature added by: Markus K (KAMiKAZOW) Feature #308045, revision 1 Title: Switch to native printer config openSUSE-11.3: Unconfirmed Priority Requester: Desirable Requested by: Markus K (kamikazow) Description: openSUSE 11.2 already ditched a few YaST modules that have native (GNOME/KDE) counterparts. One of the next steps sould be printer configuration. system-config-printer-kde is a port of GNOME's system-config-printer. The latter one is already available for openSUSE. To package scp-KDE, a similar approach to the (K)Ubuntu one makes sense: Bundle the Python files used by both into a separate package (system-config-printer-common) and then make system-config-printer-gnome and system-config-printer-kde available. -- openSUSE Feature: https://features.opensuse.org/308045

1 8

[New: openFATE 308372] lib→lib32; lib64→lib
by fate_noreply＠suse.de 12 Aug '11

12 Aug '11

Feature added by: Matt Williams (Milliams) Feature #308372, revision 1 Title: lib→lib32; lib64→lib openSUSE-11.3: Unconfirmed Priority Requester: Desirable Requested by: Matt Williams (milliams) Description: Now that 64 bit machines are almost ubiquitous, how about we make openSUSE treat 64 bit libraries as the default. This is already seen in the fact that in the buld service we have default packages and then 32 bitt packages are explicitly labeled as so. I propose: * Place all 32 bit libraries in directories called lib32 (e.g. /usr/lib32 ) * Place all 64 bit libraries in directories called lib (e.g. /usr/lib ) -- openSUSE Feature: https://features.opensuse.org/308372

1 5

[openFATE 307624] Build all noarch subpackages as noarch
by fate_noreply＠suse.de 26 Jul '11

26 Jul '11

Feature added by: Pavol Rusnak (prusnak) Feature #307624, revision 1 Title: Build all noarch subpackages as noarch openSUSE-11.3: Unconfirmed Priority Requester: Important Requested by: Pavol Rusnak (prusnak) Description: The new RPM brought a feature which allows to build subpackages as noarch even when the main package is architecture dependent. By using this we could save lots of space on mirrors and media. See http://lists.opensuse.org/opensuse-factory/2009-09/msg00170.html for reference. -- openSUSE Feature: https://features.opensuse.org/307624

1 11

[openFATE 307872] CAcert root certificate as a part of openSUSE
by fate_noreply＠suse.de 26 Jul '11

26 Jul '11

Feature added by: Jaromír Červenka (Cervajz) Feature #307872, revision 1 Title: CAcert root certificate as a part of openSUSE openSUSE-11.3: Unconfirmed Priority Requester: Important Requested by: Jaromír Červenka (cervajz) Description: CAcert (http://www.cacert.org/) is organisation issuing free certificates for everyone. It could be useful, when root certificate (http://www.cacert.org/index.php?id=3) will be a standard part of openSUSE distro. A lot of people and companies (http://www.cacert.org/stats.php) using their certificates. Some other Linux/*nix distributions has CAcert root certificate also included (http://en.wikipedia.org/wiki/Cacert#Inclusion_status) . -- openSUSE Feature: https://features.opensuse.org/307872

1 8

[openFATE 307172] Remove unneeded packages
by fate_noreply＠suse.de 24 Jul '11

24 Jul '11

Feature added by: Martin Marx (nitro424) Feature #307172, revision 1 Title: Remove unneeded packages openSUSE-11.3: Unconfirmed Priority Requester: Important Requested by: Martin Marx (nitro424) Description: I need a possibility to remove unneeded, automaticly installed software (orphans). Ubuntu example: apt-get autoremove Mandriva example: urpme packagename (Invoke it simply with urpme packagename to remove a package and any packages that depend on it.) Arch Linux example: pacman -Rsn; pacman -Rsnc; pacman -Qdt; this is my favorite I like to install and try different software. After trying it, I often want to remove it completely. -- openSUSE Feature: https://features.opensuse.org/307172

1 4

[openFATE 306627] depencency tracking for uninstalling
by fate_noreply＠suse.de 24 Jul '11

24 Jul '11

Feature added by: Jacques Boulet (oneinch) Feature #306627, revision 1 Title: depencency tracking for uninstalling openSUSE-11.3: Unconfirmed Priority Requester: Important Requested by: Jacques Boulet (oneinch) Description: The openSuSE package management is virtually unbeatable in the dependency tracking for installing department. But when it comes to uninstalling it really leaves little to be desired. It would be great if YAST and zypper kept track of the dependencies that were installed for a specific package during its install and checked the dependencies during the uninstall to see if they are in use by something else or not. And if not then give the ability to remove the unused dependencies. For example I install package "Foo" the requires library "Bar." Library "Bar" is not installed so it gets installed when I install "Foo." Later I realize the package "Foo" wasn't exactly what I needed and wish to remove it. But uninstalling just removes the package "Foo" and leaves the library "Bar" sitting around unused and taking up space. So if I want to remove the library "Bar" i must do so manually. It would be great if I wish to uninstall "Foo" that the package manager would have the ability to check any dependencies that were needed and installed for package "Foo" and see if they are still needed by another package or lib and if so, keep it, and if not remove it. Also, it would be awesome if one could remove an entire package group such as uninstalling gnome or KDE. -- openSUSE Feature: https://features.opensuse.org/306627

1 4

[openFATE 306438] yast2 sw_single should provide a view of packages where no other packages depends on
by fate_noreply＠suse.de 24 Jul '11

24 Jul '11

Feature added by: Michael Calmer (mcalmer) Feature #306438, revision 1, last change by Title: yast2 sw_single should provide a view of packages where no other packages depends on openSUSE-11.2: New Priority Requester: Important Requested by: Michael Calmer (mcalmer) Description: If I want to cleanup a workstation and remove packages which I do not need anymore I be able to know some package names which I have really selected for installation. But such packages pullin some dependencies which I am not aware of and so the number of packages growth and growth. A view, which shows me all packages where no other package depends on would help me to find packages I can remove without breaking dependencies. -- openSUSE Feature: https://features.opensuse.org/306438

1 3

[openFATE 305992] Easier removal of packages installed due dependencies and not manually by user
by fate_noreply＠suse.de 24 Jul '11

24 Jul '11

Feature added by: Nikanth K (nikanth) Feature #305992, revision 1, last change by Title: Easier removal of packages installed due dependencies and not manually by user openSUSE-11.2: Unconfirmed Priority Requester: Important Requested by: Nikanth K (nikanth) Description: If one tries to install a package say "bzflag-debugsource", then due to dependency "bzflag-debuginfo" also gets installed. But later the user may not remember it and will uninstall only "bzflag-debugsource". So installing and uninstalling, "bzflag-debugsource", does not leave the system in the same state as before. It would be nice if yast2/zypper can remember the automatic package selections and prompt user when the actual packages are being uninstalled and there are no other package that is still dependent on them. Atleast a way to know the list of packages installed due to dependencies and the no of packages still dependent on them would make it easier for the user. And this list should not include packages manually installed by the user. -- openSUSE Feature: https://features.opensuse.org/305992

1 4

[openFATE 307603] Migrate x86_32 architecture to i686
by fate_noreply＠suse.de 21 Jul '11

21 Jul '11

Feature added by: Refilwe Seete (ReferenceSeete) Feature #307603, revision 1 Title: Migrate x86_32 architecture to i686 openSUSE-11.3: Unconfirmed Priority Requester: Desirable Requested by: Refilwe Seete (referenceseete) Partner organization: openSUSE.org Description: openSUSE currently builds i586 binaries with a couple exceptions. As it currently stands openSUSE 11.1 permits a Pentium 1 but requires at least 256MB of RAM with 512MB recommended [1]. The likelihood of a person having a system with an original Pentium and 256MB (esp. 512MB) of RAM is quite low. Since the i686 architecture was introduced in 1995...2010 or 2011 is a suitable time to migrate the x86_32 target architecture without adversely affecting the majority of users. The Fedora Project is making this same transition for Fedora 12 [2]. Any growing pains they experience can be used as guidance for the transition in openSUSE 11.3 or 12.0. [1] http://www.novell.com/products/opensuse/sysreqs.html [2] https://fedoraproject.org/wiki/Features/F12X86Support Business case (Partner benefit): openSUSE.org: By moving to i686, openSUSE should receive a slight performance increase while maintaining support for an incredibly broad range of x86 chips. Any boost is helpful on systems with less processing power, such as netbooks/nettops or older systems (Pentium 2, original Athlon etc.). Moving to i686 is a way to boost performance the performance of openSUSE at the margins without having to delve into experimental or otherwise under-tested methods. -- openSUSE Feature: https://features.opensuse.org/307603

1 12