Software outside the catalogue#

This page is generated from the code and must not be edited by hand.

A folder laid out like a program’s that no program Ingence knows matches is asked about: is it a program or not?.

software_outside_the_catalogue version 1+d1

  • Kind of rule: What is raised for attention (flags). Raises something for a person’s attention without concluding anything.

  • What it concludes: a finding

  • Reasoning: defeasible. A conclusion is usually right, and is retracted when a rule it names concludes against it.

  • What it reads: one folder at a time

Is it available in this version?#

Yes. The engine runs it.

What would defeat it#

A finding is never withdrawn. When any of these rules also concludes about the same thing, the finding records it:

  • installed_software_in_folder: A folder is recognized as an installed program, such as a copy of Fiji or a Python environment, from the parts it holds, a name ending .app, its program-style subfolders or a majority of program files; its files are still indexed and read, and rules about experiments leave them alone.

It stands aside beneath every folder one of these rules raises:

Parameters#

Parameter

Shipped value

May be

What it does

layout_folder_names

["bin", "sbin", "lib", "lib64", "libexec", "include", "plugins", "jars", "Frameworks", "site-packages"]

list of text

Folder names packaging gives a program’s parts.

program_extensions

["so", "dylib", "dll", "a", "o", "lib", "pyd", "class", "jar", "exe", "h", "hpp"]

list of text

Compiled code, libraries and headers, never a script.

marker_names

["license", "licence", "copying", "version", "changelog"]

list of text

A program’s papers, compared without their extension.

bundle_name_suffixes

[".app"]

list of text

Endings of a folder’s name that packaging gives a program.

minimum_evidence

2

whole number, from 1 to 3

How many of the three kinds of structure it shows.