... Fresh Open Source Software mainly for Internet, Engineering and Science ...
Special features of the "Fossies" software archive
The "Fossies" software archive not only allows the "pure" download
of software packages but also provides, among many other features, the ability to browse and search within
the individual member files of the software packages in order to study for e.g.
the READMEs and other documentation or to download selected individual files (e.g.
images or libraries). This may avoid unnecessary file transfers and installation effort
and may let you detect some otherwise undetected open source software treasures
(that we name "fossies").
You may click "simply" on the download icon in front of a package (archive)
name in order to transfer that package but the "Fossies" software archive offers the following
additional special features to you:
And last but not least: The term "Fresh" (original derived from "FREeware SHareware")
is at the same time one of our missions so we have developed
different control techniques to archive and support always the freshest releases.
As an special feature of the Fossies service you may click on
an archive name
in order to view the contents of that archive within a special page.
That page gives you also the possibility to see all archive member files in different sort orders, via a menu line for e.g. like that:
As an additional - originally (Dec. 1994) probably world-wide unique -
feature of the Fossies server
you may click within the displayed archive index on any
member name in order to browse or download that selected member.
The server tries to send an appropriate "Content-type" header field
("mime-type") according to the member's file
extension (default: text/html). For example clicking on a GIF
file (embedded in an archive file) lets see you the image via your
browser or an external viewer without downloading the complete,
possibly large archive file.
As a further newer special service some documentation-related files are
presented more "user-friendly" respectively "readable" by trying a local
pre-formatting (only in standard "automatic"-mode):
Unix/Linux manual pages
Perl POD documentation files
GNU Texinfo documentation files
Also pure HTML files are forced to be formatted if meaningful but
HTML code for e.g. in PHP or Perl code are forced to be displayed
as unformatted source code.
Additionally most programming language, markup language and configuration files
are shown with line numbering and syntax highlighting.
In order to view the "pure" source code file you may force a simple text
transfer ("Content-type: text/plain") for e.g by clicking on the first letter
of a member's "file name" within an archive file list.
In order to force a binary transfer ("Content-type: application/octet-stream")
you may click on the member's "file size" field instead of the member's "file name".
Remark: This feature uses on-the-fly expansion and displaying the
requested member may take some seconds according the archive size.
Repeated requests are answered immediately.
In that page you can see all the member files of an archive in different listing orders,
and browse/download that members.
That page allows also the archive download in different archive formats respectively
newer not yet common but more effective compression types:
As a further special feature you can view a so-called
CLOC ("Count Lines of Code")
statistics that counts physical lines of source code in many programming languages
and in addition comments and blank lines, so you can get quickly an overview
about the scale of the project and the used program languages.
As a new (Jan. 2011) advanced feature - especially useful for developers - Fossies offers now
Doxygen generated source code documentation for most archives
respectively software packages (cross referencing documentation and code).
Although Doxygen isn't package specific customized here we hope that it would be nevertheless helpful
for understanding code structures and detecting dependencies - especially for large projects. And it may encourage authors or
package maintainers to create her own specific and thereby probably improved Doxygen documentation.
Doxygen generates amongst others a class browser and tries to extract the code-structure also
from undocumented source files.
This includes dependency graphs
(see an example here),
class diagrams and hyperlinked syntax-highlighted source code
(latter as an alternative to the orign Fossies offered source code browsing using the program
Doxygen documentation is extracted directly from the sources, which makes it much easier to keep
the documentation consistent with the source code.
The Fossies generated Doxygen documentation can be accessed via the respective package contents pages
or more directly via URls like
Files that are recently inserted in the software archive are marked by two small icons:
file is not older than 7 days
file is not older than 31 days
Archive-insertion-time sorted index
Standardally the archive index is sorted by the archive-insertion-time
(not the modified time) in order to get in a clearly arranged matter
information about recently archived software.
Alternate alphabetically sorted index
Beside the "standard" archive-insertion-time sorted archive index you may
select an alternate alphabetically sorted index.
Advanced search facility
In order to find a given software package or file you may
search recursively starting at the current archive directory.
The optional use of different approximative search modes
and the optional inclusion of file description texts into the search
space may let you find a match
even if you don't remember a filename exactly (e.g. "mosaik"
instead of "Mosaic") or if you search for a more generic term
You may specify the
archive description texts
archive internal documentation files
max. one or two allowed errors
search depth (search in underlying directories)
and limit the search for archive members with an archive insertion time
not older than a given range.
Searching in the archive internal documentation files outputs
not only the found documentation files but also a
user specified number of matching lines. Browsing
a found documentation file displays at the top of the
document the first 10 matching lines with anchors into the file and
tries to mark the matches as bolded strings.
The total number of displayed matches may be limited. Consecutive
requests for the display of suppressed matches - with optionally
different limits - are supported.
Attention: The search-syntax is currently NOT "google"-like, here are some simple examples:
would search for a line containg the exact string "foo bar"
would search for a line containing first "foo" and than "bar"
foo and bar
would search for a line containing "foo" and "bar"
foo or bar
would search for a line containing "foo" or "bar"
Additionally the character ^ matches the starting position,
the character $ the ending position. So
would search for a line starting with "bar" but wouldn't match
a line starting for e.g. with "foobar"
The search string must contain at least four "relevant" characters if searching within the archives internal doc files,
three if searching within the archive short descriptions and two if searching for filenames.
The archive maintainer can add short descriptions to individual
archive files in order to make it easier for the user to
evaluate the type and use of a given archive file
respectively software package. In a second step the user can
take advantage of the special browsing features to study READMEs or
other appropriate internal documentation.
The above descripted features are enabled by software
written by Jens Schleusener
mainly in his spare time - while employed at the
Central Division Data Processing of the German Aerospace Center (DLR)
which division is now incorporated in the
T-Systems Solutions for Research GmbH
That software consists mainly of two core components:
warix (Www ARchive IndeXer)
the preprocessing script generating the "static" index pages and the internal databases
warex (Www ARchive EXecutor)
the accompanying CGI-script processing the "dynamic" output requests.
Furthermore the Fossies software archive itself benefits awfully from many great open source
software products. Especially to be mentioned: