Communities

Writing
Writing
Codidact Meta
Codidact Meta
The Great Outdoors
The Great Outdoors
Photography & Video
Photography & Video
Scientific Speculation
Scientific Speculation
Cooking
Cooking
Electrical Engineering
Electrical Engineering
Judaism
Judaism
Languages & Linguistics
Languages & Linguistics
Software Development
Software Development
Mathematics
Mathematics
Christianity
Christianity
Code Golf
Code Golf
Music
Music
Physics
Physics
Linux Systems
Linux Systems
Power Users
Power Users
Tabletop RPGs
Tabletop RPGs
Community Proposals
Community Proposals
tag:snake search within a tag
answers:0 unanswered questions
user:xxxx search by author id
score:0.5 posts with 0.5+ score
"snake oil" exact phrase
votes:4 posts with 4+ votes
created:<1w created < 1 week ago
post_type:xxxx type of post
Search help
Notifications
Mark all as read See all your notifications »
Q&A

Comments on How to identify and separate standalone applications from libraries in Linux package lists?

Post

How to identify and separate standalone applications from libraries in Linux package lists?

+1
−0

I want to generate a list of trending Arch/AUR packages that focuses on user-facing applications rather than background libraries and dependencies.

I wrote a script that uses the data from pkgstats to show packages sorted by popularity. However, it doesn't distinguish between applications and libraries, so the output isn't very useful.

I want to identify and separate standalone applications from libraries and dependencies for both Arch official repositories and AUR packages. Not just for installed packages but for all of them.

pamac, Graphical Package Manager for Manjaro Linux with Alpm, AUR, Appstream, Flatpak and Snap support, seems to identify applications vs libraries/dependencies when grouping packages into categories like "Music & Audio" or "Games". As seen in this code, pamac gets categorized package lists and populates the UI accordingly.

Since it may not be clear what libraries or dependencies are and I'm already using pamac as an example. I'll consider packages that appear in pamac's categories like Games and Music & Audio as applications, and other packages as libraries/dependencies.

As an alternative, I would consider end-user software the ones that aren't required by any other packages. This isn't perfect, just good enough. For example, this is how I would do this for installed packages.

How can I identify standalone applications and separate them from libraries/dependencies in the Arch/AUR package lists? The end goal is a trending packages list focused on end-user software rather than background components.

History
Why does this post require attention from curators or moderators?
You might want to add some details to your flag.
Why should this post be closed?

1 comment thread

Definitions? (2 comments)
Definitions?
Karl Knechtel‭ wrote about 1 year ago · edited about 1 year ago

(It looks like you've already considered this, but.)

While I'm interested in this task and agree that there's at least an intuitive distinction to be drawn between libraries and applications, I'm not sure that there's a rigorous way to defined that distinction that's good enough for a programmatic approach (unless perhaps there's some metadata to parse somewhere). The best I can think of is to apply the label "application" to anything that isn't cited as a dependency by anything else; that would misclassify some attempts at libraries by nobodies that haven't been tried by others yet, but that wouldn't be a problem for this kind of "trending" list.

H_H‭ wrote about 1 year ago

isn't cited as a dependency by anything else;

Not sure about Arch but on debian, you may have applications like konsole, for which a packet exist, and then there are packets like kde-baseapps that depend on konsole.

Metapackage like kde-baseapps are intended to bundle multiple packets together. Maybe you can filter for metapackage somehow, but don't ask me how.