AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |
Back to Blog
Bzflag server3/25/2023 Any boost is helpful on systems with less processing power, such as netbooks/nettops or older systems (Pentium 2, original Athlon etc.). : By moving to i686, openSUSE should receive a slight performance increase while maintaining support for an incredibly broad range of x86 chips. Any growing pains they experience can be used as guidance for the transition in openSUSE 11.3 or 12.0. The Fedora Project is making this same transition for Fedora 12. 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 likelihood of a person having a system with an original Pentium and 256MB (esp. As it currently stands openSUSE 11.1 permits a Pentium 1 but requires at least 256MB of RAM with 512MB recommended. OpenSUSE currently builds i586 binaries with a couple exceptions. Requested by: Refilwe Seete (referenceseete) Title: Migrate x86_32 architecture to i686 And this list should not include packages manually installed by the user.įeature added by: Refilwe Seete (ReferenceSeete) 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.Ītleast 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. So installing and uninstalling, "bzflag-debugsource", does not leave the system in the same state as before. But later the user may not remember it and will uninstall only "bzflag-debugsource". If one tries to install a package say "bzflag-debugsource", then due to dependency "bzflag-debuginfo" also gets installed. Title: Easier removal of packages installed due dependencies and not manually by user 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.Īlso, it would be awesome if one could remove an entire package group such as uninstalling gnome or KDE.įeature #305992, revision 1, last change by So if I want to remove the library "Bar" i must do so manually. But uninstalling just removes the package "Foo" and leaves the library "Bar" sitting around unused and taking up space. And if not then give the ability to remove the unused dependencies.įor 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. 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. But when it comes to uninstalling it really leaves little to be desired. The openSuSE package management is virtually unbeatable in the dependency tracking for installing department. Title: depencency tracking for uninstalling usr/share/doc/bzflag-server/examples/ added by: Jacques Boulet (oneinch) usr/share/doc/bzflag-server/examples/fountains.bzw usr/share/doc/bzflag-server/examples/flagbuffet.bzw usr/share/doc/bzflag-server/README.Debian usr/lib/bzflag-server/serverSidePlayerSample.so usr/lib/bzflag-server/playHistoryTracker.so usr/lib/bzflag-server/customflagsample.so usr/lib/bzflag-server/customPollTypeSample.so usr/lib/bzflag-server/CustomZoneSample.so Information about the apt package "bzflag-server".
0 Comments
Read More
Leave a Reply. |