Language Selection

English French German Italian Portuguese Spanish

GNOME Debian Package Finder: Rough and ready package search for the desktop

Filed under
Software

If you do your Debian package management from the command line, you are probably aware of utilities that search the cache of available programs, such as apt-cache, apt-file, and dpkg. Possibly, too, you have cursed the limited search information available in graphical interfaces like Synaptic, which does not extend much beyond searching for the description, name, versions, and dependencies. Now, the GNOME Debian Package Finder (gpfind) is in the process of bring much of the command-line search capacity to the desktop -- although, at version 0.1.6, it is still too rough to replace its command-line equivalents for most users.

The roughness begins with installation. Although packages are available for Debian and Ubuntu, the major distributions that use the Debian package system, they do not have automatic dependency resolution. Instead, you need to install libconfig-file-perl, libapt-pkg-perl, liblist-moreutils-perl, and perl-base before using dpkg -i to install gpfind. After installing gpfind, you also need to run the command apt-file update before a search for files inside packages will return anything except a blank screen.

More Here




More in Tux Machines

Simon Phipps on Public Domain and Facebook’s React Licence

  • Public Domain Is Not Open Source
    Open Source and Public Domain are frequently confused. Here’s why it’s a mistake to treat the two terms as synonyms. Plenty of people assume that public domain software must be open source. While it may be free software within your specific context, it is incorrect to treat public domain software as open source or indeed as globally free software. That’s not a legal opinion (I’m not a lawyer so only entitled to layman’s opinions) but rather an observation that an open source user or developer cannot safely include public domain source code in a project.
  • 5 Reasons Facebook’s React License Was A Mistake
    In July 2017, the Apache Software Foundation effectively banned the license combination Facebook has been applying to all the projects it has been releasing as open source. They are using the 3-clause BSD license (BSD-3), a widely-used OSI-approved non-reciprocal license, combined with a broad, non-reciprocal patent grant but with equally broad termination rules to frustrate aggressors. The combination represents a new open source license, which I’ve termed the “Facebook BSD Plus Patent License” (FB+PL), and to my eyes it bears the hallmarks of an attempt to be compatible with both the GPL v2 and the Apache License v2 at the same time, in circumvention of the alleged imcompatibility of those licenses.

Red Hat Shares/Stock News

AMD With Linux: AMDGPU, AMDGPU-PRO, and RadeonSI

Games for GNU/Linux