Differences between revisions 24 and 25
Revision 24 as of 2021-08-27 07:18:22
Size: 5424
Editor: ?MichaelStapelberg
Comment: add testimonial from Ingo Schwarze (as per Ingo’s request)
Revision 25 as of 2021-09-15 08:14:14
Size: 5674
Comment: provide my testimony
Deletions are marked like this. Additions are marked like this.
Line 37: Line 37:
 * I frequently use codesearch.d.o - most notably for the development of DebianPackage:licensecheck and related libraries, where the ability to apply regular expression patterns to the whole set of Debian-packages source code is imensely helpful.

Debian Code Search



In case codesearch was helpful for you, please make others aware of it by posting a short testimonial. Feel free to add yours to this list:

  • I often use codesearch to find examples for specific features that are not very well documented, like DEP-3 patch tags. -- Michael Stapelberg, Debian Developer
  • https://sources.debian.net allows to browse trough the source code of all Debian packages. Having that, it just comes natural to viewers of the website to do searches through all that mass of source code. Integrating with codesearch made that trivial to achieve. Thanks for it! -- Stefano Zacchiroli, Debian Developer

  • I use codesearch to find out whether external kernel modules are using a function and whether an ABI change in the function requires a new kernel module ABI number. -- Ben Hutchings, Debian Developer
  • I use Debian Code Search to find out how to use underdocumented APIs, and to see how others are actually using the APIs I provide. It's also quite useful to gauge the adoption of various algorithms, features, libraries, and APIs. -- Nick Mathewson, developer, Tor and Libevent
  • For planning (library) transitions, codesearch has become an invaluable tool to me. I use it regularly, to check for users of certain library APIs, D-Bus interfaces or packages calling binaries. -- Michael Biebl
  • codesearch.d.n and sources.d.n are the tools I have been dreaming for years! Thank you -- Ana Guerrero Lopez, Debian Developer
  • I use codesearch frequently (multiple times a week) at work and also for release work to find where some specific code is used and how it is used. It's also very helpful to check for dependencies on e.g. essential packages very quickly. -- Philipp Kern, Debian Developer
  • The QA work I am doing both as part of my work/research (see BTS usertag goto-cc) and as DD would be a lot less efficient without the combination of codesearch.d.n and sources.d.n. Also I'm now frequently pointing non-Debian co-workers at either of the two to quickly get an idea about certain aspects of software. Thanks you!! -- Michael Tautschnig, Debian Developer
  • I use codesearch to look for common security vulnerabilities, and to find patterns of library misuse. It is a great help in improving the quality of the archive! I also use it to help library upstreams plan API transitions. Being able to quickly tell an upstream the difference between "if you drop this interface, 15 packages in debian won't be able to move to your new API without their own changes" and "that interface isn't used by any package in debian" is a great thing. -- Daniel Kahn Gillmor, Debian Developer
  • codesearch is becomming an essential part of the Debian infrastructure, that allows one to quickly answer questions that would otherwise have needed tedious greps in the Lintian lab. Another very positive impact of codesearch is that it structures technical discussions on our mailing lists, where there is no exuse anymore for writing some statements about our archive's contents without testing them concretely. Thus, codesearch quickly gets people to the facts, which is essential for Debian's aims of technical excellence. -- CharlesPlessy, Debian Developer

  • Debian's code search is valuable for free software developers outside of your community. I use this service as part of OpenBSD's continuous effort to identify buggy or insecure API calls. If we see a function being abused in our tree, DCS lets us quickly see how widespread the problem is. When we introduce safer alternatives, we can track how quickly projects convert. I also use it to determine how safe it is to remove legacy API functions from LibreSSL. I have tried most of the code indexing sites available, and Debian's provides the most relevant results for us. Thanks for making this service available to non-DDs. -- Doug Hogan, OpenBSD developer
  • Code search made so much possible for ReproducibleBuilds. So much data love! -- Lunar

  • I use code search frequently - it's an amazing tool when making Debian wide changes. For example, it provides an easy way to check what packages call a particular m4 macro. The implementation of the Janitor would have been much harder without DebianCodeSearch. -- Jelmer Vernooij, Debian Developer

  • When documenting API functions in LibreSSL, i consistently and very frequently use Debian Code Search to find out whether a given function is actually used in any real-world software. Functions that see real-world use should be documented; those that don't should remain undocumented, to avoid needless bloat of the manual. Debian Code Search is ideal for this purpose due to the vast amount of code indexed, its easy-to-use user interface, and its simple and straightforward output format. -- Ingo Schwarze, OpenBSD developer and chief LibreSSL documentation maintainer
  • I frequently use codesearch.d.o - most notably for the development of licensecheck and related libraries, where the ability to apply regular expression patterns to the whole set of Debian-packages source code is imensely helpful.

Accepted Feature requests

Please see https://github.com/Debian/dcs/issues for sending new feature requests.

filetype keyword

The filetype keyword filters by programming language. The following values are currently implemented:

c: .c, .h

c++: .cpp, .cxx, .hpp, .hxx, .h, .c

perl: .pl, .pm, .t

python: .py

go (or golang): .go

java: .java

ruby: .rb

shell: .sh, .bash, .zsh