How can I find out in which distributions a package is available?

The name of the pictureThe name of the pictureThe name of the pictureClash Royale CLAN TAG#URR8PPP











up vote
2
down vote

favorite












From the search results I was able to get so far my question seems unlikely, although I don't know why ;-)



I'm writing an installation guide for a program and need a “compatibility matrix” for several packages on the different distributions. So what I need is the information in which distributions and releases a given package X is available, optionally together with the version.



Of course each distribution has a package index like Debian Packages Search from where I can get the information for this distribution. But is there an index or a search engine anywhere that can give me this information for many (all?) distributions?







share|improve this question






















  • There isn't, though someone set up something like that a few years ago - see byacc summary on the Web Archive for example.
    – Thomas Dickey
    Jan 14 at 22:40










  • rmadison may be of use for Debian and its ilk - manpages.ubuntu.com/manpages/trusty/man1/rmadison.1.html
    – ivanivan
    Jan 14 at 23:18














up vote
2
down vote

favorite












From the search results I was able to get so far my question seems unlikely, although I don't know why ;-)



I'm writing an installation guide for a program and need a “compatibility matrix” for several packages on the different distributions. So what I need is the information in which distributions and releases a given package X is available, optionally together with the version.



Of course each distribution has a package index like Debian Packages Search from where I can get the information for this distribution. But is there an index or a search engine anywhere that can give me this information for many (all?) distributions?







share|improve this question






















  • There isn't, though someone set up something like that a few years ago - see byacc summary on the Web Archive for example.
    – Thomas Dickey
    Jan 14 at 22:40










  • rmadison may be of use for Debian and its ilk - manpages.ubuntu.com/manpages/trusty/man1/rmadison.1.html
    – ivanivan
    Jan 14 at 23:18












up vote
2
down vote

favorite









up vote
2
down vote

favorite











From the search results I was able to get so far my question seems unlikely, although I don't know why ;-)



I'm writing an installation guide for a program and need a “compatibility matrix” for several packages on the different distributions. So what I need is the information in which distributions and releases a given package X is available, optionally together with the version.



Of course each distribution has a package index like Debian Packages Search from where I can get the information for this distribution. But is there an index or a search engine anywhere that can give me this information for many (all?) distributions?







share|improve this question














From the search results I was able to get so far my question seems unlikely, although I don't know why ;-)



I'm writing an installation guide for a program and need a “compatibility matrix” for several packages on the different distributions. So what I need is the information in which distributions and releases a given package X is available, optionally together with the version.



Of course each distribution has a package index like Debian Packages Search from where I can get the information for this distribution. But is there an index or a search engine anywhere that can give me this information for many (all?) distributions?









share|improve this question













share|improve this question




share|improve this question








edited Jan 15 at 7:56









GAD3R

22.5k154894




22.5k154894










asked Jan 14 at 22:17









uli_1973

1143




1143











  • There isn't, though someone set up something like that a few years ago - see byacc summary on the Web Archive for example.
    – Thomas Dickey
    Jan 14 at 22:40










  • rmadison may be of use for Debian and its ilk - manpages.ubuntu.com/manpages/trusty/man1/rmadison.1.html
    – ivanivan
    Jan 14 at 23:18
















  • There isn't, though someone set up something like that a few years ago - see byacc summary on the Web Archive for example.
    – Thomas Dickey
    Jan 14 at 22:40










  • rmadison may be of use for Debian and its ilk - manpages.ubuntu.com/manpages/trusty/man1/rmadison.1.html
    – ivanivan
    Jan 14 at 23:18















There isn't, though someone set up something like that a few years ago - see byacc summary on the Web Archive for example.
– Thomas Dickey
Jan 14 at 22:40




There isn't, though someone set up something like that a few years ago - see byacc summary on the Web Archive for example.
– Thomas Dickey
Jan 14 at 22:40












rmadison may be of use for Debian and its ilk - manpages.ubuntu.com/manpages/trusty/man1/rmadison.1.html
– ivanivan
Jan 14 at 23:18




rmadison may be of use for Debian and its ilk - manpages.ubuntu.com/manpages/trusty/man1/rmadison.1.html
– ivanivan
Jan 14 at 23:18










2 Answers
2






active

oldest

votes

















up vote
0
down vote













Distrowatch offers a list of installed packages for each distro. For example (look at the tables in the middle of the page)






share|improve this answer




















  • I have found the search page on Distrowatch which is actually the functionality I need. Unfortunately it only tracks a certain number of packages - and (of course) the packages I'm interested in aren't among them.
    – uli_1973
    Jan 16 at 8:08

















up vote
0
down vote













Repology is an online service which seems to fit the bill. Its information is accurate for the packages I checked, but other commentators differ.



You might also find whohas useful. This is a tool which runs locally and interrogates a number of package indexes directly.



Both tools track most of the major distributions; Repology indexes lots of smaller ones too.



Can I depend? provides a list of supported versions for a small set of language runtimes on a few distributions (Debian, Ubuntu, RHEL, SLES). Its scope is much smaller than Repology’s but it could be sufficient for some readers.






share|improve this answer






















  • Interesting, but comparing with my programs, the first is noticeably inaccurate (I'm not going to use it). The other would take more time to investigate.
    – Thomas Dickey
    Jan 15 at 1:09










  • For which packages did you find errors? I looked at xterm among others and the results seem accurate. (I’m not trying to argue, I’m genuinely curious.)
    – Stephen Kitt
    Jan 15 at 5:42










  • I started with luit, and saw that some of my work was misattributed, looked at cdk (wrong version numbers). Commenting now, there's bogus information for bcpp, vttest. Also, judging by the results, it's Linux-specific, which is misleading since it implies more independence across packagers than exists, and ignores the other 60% of the packaging domain.
    – Thomas Dickey
    Jan 15 at 10:40










  • Oh OK, I see, thanks. It does have info on MacPorts, FreeBSD ports, and OpenIndiana, so it’s not Linux-specific, but most of the results are for Linux distributions.
    – Stephen Kitt
    Jan 15 at 10:43










  • See the GitHub repo for coverage details.
    – Stephen Kitt
    Jan 15 at 10:44










Your Answer







StackExchange.ready(function()
var channelOptions =
tags: "".split(" "),
id: "106"
;
initTagRenderer("".split(" "), "".split(" "), channelOptions);

StackExchange.using("externalEditor", function()
// Have to fire editor after snippets, if snippets enabled
if (StackExchange.settings.snippets.snippetsEnabled)
StackExchange.using("snippets", function()
createEditor();
);

else
createEditor();

);

function createEditor()
StackExchange.prepareEditor(
heartbeatType: 'answer',
convertImagesToLinks: false,
noModals: false,
showLowRepImageUploadWarning: true,
reputationToPostImages: null,
bindNavPrevention: true,
postfix: "",
onDemand: true,
discardSelector: ".discard-answer"
,immediatelyShowMarkdownHelp:true
);



);








 

draft saved


draft discarded


















StackExchange.ready(
function ()
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2funix.stackexchange.com%2fquestions%2f417128%2fhow-can-i-find-out-in-which-distributions-a-package-is-available%23new-answer', 'question_page');

);

Post as a guest






























2 Answers
2






active

oldest

votes








2 Answers
2






active

oldest

votes









active

oldest

votes






active

oldest

votes








up vote
0
down vote













Distrowatch offers a list of installed packages for each distro. For example (look at the tables in the middle of the page)






share|improve this answer




















  • I have found the search page on Distrowatch which is actually the functionality I need. Unfortunately it only tracks a certain number of packages - and (of course) the packages I'm interested in aren't among them.
    – uli_1973
    Jan 16 at 8:08














up vote
0
down vote













Distrowatch offers a list of installed packages for each distro. For example (look at the tables in the middle of the page)






share|improve this answer




















  • I have found the search page on Distrowatch which is actually the functionality I need. Unfortunately it only tracks a certain number of packages - and (of course) the packages I'm interested in aren't among them.
    – uli_1973
    Jan 16 at 8:08












up vote
0
down vote










up vote
0
down vote









Distrowatch offers a list of installed packages for each distro. For example (look at the tables in the middle of the page)






share|improve this answer












Distrowatch offers a list of installed packages for each distro. For example (look at the tables in the middle of the page)







share|improve this answer












share|improve this answer



share|improve this answer










answered Jan 15 at 2:49









Isaac

6,7611834




6,7611834











  • I have found the search page on Distrowatch which is actually the functionality I need. Unfortunately it only tracks a certain number of packages - and (of course) the packages I'm interested in aren't among them.
    – uli_1973
    Jan 16 at 8:08
















  • I have found the search page on Distrowatch which is actually the functionality I need. Unfortunately it only tracks a certain number of packages - and (of course) the packages I'm interested in aren't among them.
    – uli_1973
    Jan 16 at 8:08















I have found the search page on Distrowatch which is actually the functionality I need. Unfortunately it only tracks a certain number of packages - and (of course) the packages I'm interested in aren't among them.
– uli_1973
Jan 16 at 8:08




I have found the search page on Distrowatch which is actually the functionality I need. Unfortunately it only tracks a certain number of packages - and (of course) the packages I'm interested in aren't among them.
– uli_1973
Jan 16 at 8:08












up vote
0
down vote













Repology is an online service which seems to fit the bill. Its information is accurate for the packages I checked, but other commentators differ.



You might also find whohas useful. This is a tool which runs locally and interrogates a number of package indexes directly.



Both tools track most of the major distributions; Repology indexes lots of smaller ones too.



Can I depend? provides a list of supported versions for a small set of language runtimes on a few distributions (Debian, Ubuntu, RHEL, SLES). Its scope is much smaller than Repology’s but it could be sufficient for some readers.






share|improve this answer






















  • Interesting, but comparing with my programs, the first is noticeably inaccurate (I'm not going to use it). The other would take more time to investigate.
    – Thomas Dickey
    Jan 15 at 1:09










  • For which packages did you find errors? I looked at xterm among others and the results seem accurate. (I’m not trying to argue, I’m genuinely curious.)
    – Stephen Kitt
    Jan 15 at 5:42










  • I started with luit, and saw that some of my work was misattributed, looked at cdk (wrong version numbers). Commenting now, there's bogus information for bcpp, vttest. Also, judging by the results, it's Linux-specific, which is misleading since it implies more independence across packagers than exists, and ignores the other 60% of the packaging domain.
    – Thomas Dickey
    Jan 15 at 10:40










  • Oh OK, I see, thanks. It does have info on MacPorts, FreeBSD ports, and OpenIndiana, so it’s not Linux-specific, but most of the results are for Linux distributions.
    – Stephen Kitt
    Jan 15 at 10:43










  • See the GitHub repo for coverage details.
    – Stephen Kitt
    Jan 15 at 10:44














up vote
0
down vote













Repology is an online service which seems to fit the bill. Its information is accurate for the packages I checked, but other commentators differ.



You might also find whohas useful. This is a tool which runs locally and interrogates a number of package indexes directly.



Both tools track most of the major distributions; Repology indexes lots of smaller ones too.



Can I depend? provides a list of supported versions for a small set of language runtimes on a few distributions (Debian, Ubuntu, RHEL, SLES). Its scope is much smaller than Repology’s but it could be sufficient for some readers.






share|improve this answer






















  • Interesting, but comparing with my programs, the first is noticeably inaccurate (I'm not going to use it). The other would take more time to investigate.
    – Thomas Dickey
    Jan 15 at 1:09










  • For which packages did you find errors? I looked at xterm among others and the results seem accurate. (I’m not trying to argue, I’m genuinely curious.)
    – Stephen Kitt
    Jan 15 at 5:42










  • I started with luit, and saw that some of my work was misattributed, looked at cdk (wrong version numbers). Commenting now, there's bogus information for bcpp, vttest. Also, judging by the results, it's Linux-specific, which is misleading since it implies more independence across packagers than exists, and ignores the other 60% of the packaging domain.
    – Thomas Dickey
    Jan 15 at 10:40










  • Oh OK, I see, thanks. It does have info on MacPorts, FreeBSD ports, and OpenIndiana, so it’s not Linux-specific, but most of the results are for Linux distributions.
    – Stephen Kitt
    Jan 15 at 10:43










  • See the GitHub repo for coverage details.
    – Stephen Kitt
    Jan 15 at 10:44












up vote
0
down vote










up vote
0
down vote









Repology is an online service which seems to fit the bill. Its information is accurate for the packages I checked, but other commentators differ.



You might also find whohas useful. This is a tool which runs locally and interrogates a number of package indexes directly.



Both tools track most of the major distributions; Repology indexes lots of smaller ones too.



Can I depend? provides a list of supported versions for a small set of language runtimes on a few distributions (Debian, Ubuntu, RHEL, SLES). Its scope is much smaller than Repology’s but it could be sufficient for some readers.






share|improve this answer














Repology is an online service which seems to fit the bill. Its information is accurate for the packages I checked, but other commentators differ.



You might also find whohas useful. This is a tool which runs locally and interrogates a number of package indexes directly.



Both tools track most of the major distributions; Repology indexes lots of smaller ones too.



Can I depend? provides a list of supported versions for a small set of language runtimes on a few distributions (Debian, Ubuntu, RHEL, SLES). Its scope is much smaller than Repology’s but it could be sufficient for some readers.







share|improve this answer














share|improve this answer



share|improve this answer








edited Jan 15 at 10:10

























answered Jan 14 at 22:58









Stephen Kitt

142k22308371




142k22308371











  • Interesting, but comparing with my programs, the first is noticeably inaccurate (I'm not going to use it). The other would take more time to investigate.
    – Thomas Dickey
    Jan 15 at 1:09










  • For which packages did you find errors? I looked at xterm among others and the results seem accurate. (I’m not trying to argue, I’m genuinely curious.)
    – Stephen Kitt
    Jan 15 at 5:42










  • I started with luit, and saw that some of my work was misattributed, looked at cdk (wrong version numbers). Commenting now, there's bogus information for bcpp, vttest. Also, judging by the results, it's Linux-specific, which is misleading since it implies more independence across packagers than exists, and ignores the other 60% of the packaging domain.
    – Thomas Dickey
    Jan 15 at 10:40










  • Oh OK, I see, thanks. It does have info on MacPorts, FreeBSD ports, and OpenIndiana, so it’s not Linux-specific, but most of the results are for Linux distributions.
    – Stephen Kitt
    Jan 15 at 10:43










  • See the GitHub repo for coverage details.
    – Stephen Kitt
    Jan 15 at 10:44
















  • Interesting, but comparing with my programs, the first is noticeably inaccurate (I'm not going to use it). The other would take more time to investigate.
    – Thomas Dickey
    Jan 15 at 1:09










  • For which packages did you find errors? I looked at xterm among others and the results seem accurate. (I’m not trying to argue, I’m genuinely curious.)
    – Stephen Kitt
    Jan 15 at 5:42










  • I started with luit, and saw that some of my work was misattributed, looked at cdk (wrong version numbers). Commenting now, there's bogus information for bcpp, vttest. Also, judging by the results, it's Linux-specific, which is misleading since it implies more independence across packagers than exists, and ignores the other 60% of the packaging domain.
    – Thomas Dickey
    Jan 15 at 10:40










  • Oh OK, I see, thanks. It does have info on MacPorts, FreeBSD ports, and OpenIndiana, so it’s not Linux-specific, but most of the results are for Linux distributions.
    – Stephen Kitt
    Jan 15 at 10:43










  • See the GitHub repo for coverage details.
    – Stephen Kitt
    Jan 15 at 10:44















Interesting, but comparing with my programs, the first is noticeably inaccurate (I'm not going to use it). The other would take more time to investigate.
– Thomas Dickey
Jan 15 at 1:09




Interesting, but comparing with my programs, the first is noticeably inaccurate (I'm not going to use it). The other would take more time to investigate.
– Thomas Dickey
Jan 15 at 1:09












For which packages did you find errors? I looked at xterm among others and the results seem accurate. (I’m not trying to argue, I’m genuinely curious.)
– Stephen Kitt
Jan 15 at 5:42




For which packages did you find errors? I looked at xterm among others and the results seem accurate. (I’m not trying to argue, I’m genuinely curious.)
– Stephen Kitt
Jan 15 at 5:42












I started with luit, and saw that some of my work was misattributed, looked at cdk (wrong version numbers). Commenting now, there's bogus information for bcpp, vttest. Also, judging by the results, it's Linux-specific, which is misleading since it implies more independence across packagers than exists, and ignores the other 60% of the packaging domain.
– Thomas Dickey
Jan 15 at 10:40




I started with luit, and saw that some of my work was misattributed, looked at cdk (wrong version numbers). Commenting now, there's bogus information for bcpp, vttest. Also, judging by the results, it's Linux-specific, which is misleading since it implies more independence across packagers than exists, and ignores the other 60% of the packaging domain.
– Thomas Dickey
Jan 15 at 10:40












Oh OK, I see, thanks. It does have info on MacPorts, FreeBSD ports, and OpenIndiana, so it’s not Linux-specific, but most of the results are for Linux distributions.
– Stephen Kitt
Jan 15 at 10:43




Oh OK, I see, thanks. It does have info on MacPorts, FreeBSD ports, and OpenIndiana, so it’s not Linux-specific, but most of the results are for Linux distributions.
– Stephen Kitt
Jan 15 at 10:43












See the GitHub repo for coverage details.
– Stephen Kitt
Jan 15 at 10:44




See the GitHub repo for coverage details.
– Stephen Kitt
Jan 15 at 10:44












 

draft saved


draft discarded


























 


draft saved


draft discarded














StackExchange.ready(
function ()
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2funix.stackexchange.com%2fquestions%2f417128%2fhow-can-i-find-out-in-which-distributions-a-package-is-available%23new-answer', 'question_page');

);

Post as a guest













































































Popular posts from this blog

How to check contact read email or not when send email to Individual?

Displaying single band from multi-band raster using QGIS

How many registers does an x86_64 CPU actually have?