Shulou(Shulou.com)06/01 Report--

This article mainly introduces how to make Linux software installation easier, with a certain reference value, interested friends can refer to, I hope you can learn a lot after reading this article, the following let Xiaobian take you to understand.

1. Open source is not just source code.

"it's open source, this is the source code." May be ignored. Most users don't really need the source code, they want a binary file. Developers should package their programs in advance, and they really need to be encouraged to do so.

two。 How to run

"I've installed Foo, but how do I run it?" I'm afraid there are few people who haven't seen similar questions on the relevant forums. All window managers that follow the Freedesktop.org standard follow the standard XDG desktop file rules for menu entries. Install a graphical program and you don't have to complain.

3. Standardized interface

Forget the debate about the format of the file package, it will never happen. We need a standard package graphical interface manager that can install all packages. Imagine that Synaptic runs on Ubuntu and Fedora, and it would be nice to know whether to use the Debs package or RPMs package format.

4. Easier to add software repository repositories

Add repositories, often by copying and pasting long, mysterious text strings from the browser to the terminal. A standard repository file causes the browser to launch the appropriate package manager to add it to repository, and a dialog box "are you sure/do you trust this" appears.

5. Easier source code compilation

How many programs do not have a compiler and installation instructions? Many of them have general automatic generation tools. It's easy. So why not generate an Install.sh script for the user? At the same time, check the dependency relationship.

6.Autotools = yuck

Autotools is slow and looks mysterious. Developers mainly use Autotools. End users should not see such a thing.

7. Reduce file system clutter

Is it really necessary to install files in a dazzling directory? It is a good idea to install the program from the package manager, and you can know who has been cleared when you uninstall it. Build source code may not be human enough when uninstalled or removed from the system, especially if the developer does not provide uninstall files.

8. Standard comprehensive package

If we can't reach an agreement on the format of a single package, how can we talk about standard package management?

9. Standard package name

Why do different distributions have different names for the same package? Wouldn't it be easier to resolve package dependencies if there were consistent names between distributions?

10. Standard package split

Not only does the software need to be named uniformly, but also the secondary packages need to be named consistently in each distribution. For upstream developers, consistency still has a long way to go.

11. Remove-dev package

When we try to compile the source code, the-dev or-devel packages containing the library header files can cause endless confusion, such as the frequent occurrence of messages like "libfoo not found". When installing GCC or Autotools, automatically installing the relevant-dev package will reduce our pain.

twelve。 Automatically complete the installation of the source code package

If each distribution requires a different package, perhaps a single source package can solve this situation. But if the package manager could download, compile, and install the source code automatically, wouldn't that address different package requirements?

13. Browser-based software package management

Now, the graphical interface of the package manager is great, but the remote installation has to go back to the command line. A software package manager running on a web browser will make it easier to browse and upgrade software on remote computers.

14. Do we need so many software packages?

Some projects have source code, as well as downloads of Deb and RPM package files. For each derivative of Ubuntu, there is its own package, not to mention the derivative version of SUSE and Fedora. Developers, is it really necessary to let poor end users fall into the abyss?

15. Non-single directory installation

Sometimes the idea of installing software in your own directory pops up. Well, it looks very attractive. But for us users, click the "install" button to run the program, and then start it on the menu.

16. Link from the web page to the software manager

In general, when you find a URL where you want to try the software, then you start looking for a package in the software manager, or risk using a package that has not been verified by the distribution. Wouldn't it be more convenient to start the package manager from URL and look for packages?

17. Run after installation

If you install a piece of software that is not running in the background, it is possible to run it as soon as the installation is complete. Wouldn't it be more convenient if a check window appears in your favorite package manager when the installation is complete? You don't have to start from the menu, just click install and run, that's all.

18. Make sure the source code is built in the package database

Not only is it a bit painful to install from the source code, but in fact, the package manager doesn't know exactly what you've installed, so dependencies are always missing and can't be solved. If there is a package manager that can be built from the source package, it will not only ease the pain of installation, but also let us know what is installed.

19. Non-full package

The application and library files are split into separate packages, causing dependencies and other problems, but this is effectively addressed by most package managers. We can also put everything in one package through the window, which means aggregating different versions of the same library files scattered in the file system.

20. Clear old dependencies

When you install the software, its dependencies are also installed. But when you remove the package, these dependencies remain in the system and gradually fill your hard drive. The package manager should not only remove unwanted dependencies, but also clean up the system at all times.

Thank you for reading this article carefully. I hope the article "how to make it easier to install Linux software" shared by the editor will be helpful to everyone. At the same time, I also hope you can support us and pay attention to the industry information channel. More related knowledge is waiting for you to learn!

Welcome to subscribe "Shulou Technology Information " to get latest news, interesting things and hot topics in the IT industry, and controls the hottest and latest Internet news, technology news and IT industry trends.