Philipp Thomas's avatar

You are behind a proxy. You can modify other data related to your profile by this link.

Philipp Thomas's avatar

Philipp Thomas

psmt

Involved Projects and Packages
Bugowner

Cabinet (.CAB) files are a form of archive, which is used by the
InstallShield installer software. The unshield program simply unpacks
such files. This is the binary executable.

Maintainer

These are the GNU core utilities. This package is the union of
the GNU fileutils, sh-utils, and textutils packages.

[ arch b2sum base32 base64 basename basenc cat chcon chgrp chmod chown chroot
cksum comm cp csplit cut date dd df dir dircolors dirname du echo env expand
expr factor false fmt fold groups head hostid id install join
link ln logname ls md5sum mkdir mkfifo mknod mktemp mv nice nl nohup
nproc numfmt od paste pathchk pinky pr printenv printf ptx pwd readlink
realpath rm rmdir runcon seq sha1sum sha224sum sha256sum sha384sum sha512sum
shred shuf sleep sort split stat stdbuf stty sum sync tac tail tee test
timeout touch tr true truncate tsort tty uname unexpand uniq unlink
uptime users vdir wc who whoami yes

Maintainer

NOTE: Automatically created during Factory devel project migration by admin.

Maintainer

NOTE: Automatically created during Factory devel project migration by admin.

Maintainer

The GNU implementation of the find utilities (find and xargs).

Maintainer

GNU awk is upwardly compatible with the
System V Release 4 awk. It is almost
completely POSIX 1003.2 compliant.

Maintainer

NOTE: Automatically created during Factory devel project migration by admin.

Maintainer Bugowner

NOTE: Automatically created during Factory devel project migration by admin.

Maintainer

SCPM enables your system to save different configurations in profiles.
You can boot directly into a profile as well as switch profiles at run
time. It is the successor of scheme management.

Maintainer

NOTE: Automatically created during Factory devel project migration by admin.

This package is based on the package 'perl-Module-Pluggable' from project 'openSUSE:Factory'.

Provides a simple but, hopefully, extensible way of having 'plug-ins'
for your module. Obviously, this is not going to be the best possible
of solutions but it is convenient at the moment.

Essentially all it does is to export a method into your namespace that
looks through a search path for .pm files and turns those into class
names.

Optionally, it instantiates those classes for you.

Maintainer Bugowner

This module lets you use special zip files, called Perl Archives, as
libraries from which Perl modules can be loaded.

This module implements the App::Packer::Backend interface, for generating
stand-alone executables, perl scripts and PAR files.

Developers hate writing documentation. They'd hate it even more if their computer tattled on them, but maybe they'll be even more thankful in the long run. Even if not, perlmodstyle tells you to, so you must obey.

This module provides a mechanism for determining if the pod for a given module is comprehensive.

It expects to find either a =head(n>1) or an =item block documenting a subroutine.

RPM::Header::PurePerl is a clone of RPM::Header written in only Perl, so it
provides a way to read a rpm package on systems where rpm is not installed.
RPM::Header::PurePerl can be used as a drop in replacement for RPM::Header,
if needed also the other way round.

RPM uses a version number sorting algorithm for some of its decisions. It's
useful to get at this sorting algoritm for other nefarious purposes if you
are using RPM at your site.

Maintainer Bugowner

Boost provides free peer-reviewed portable C++ source libraries. The emphasis is on libraries that work well with the C++ Standard Library. One goal is to establish "existing practice" and provide reference implementations so that the Boost libraries are suitable for eventual standardization. Some of the libraries have already been proposed for inclusion in the C++ Standards Committee's upcoming C++ Standard Library Technical Report.

Although Boost was begun by members of the C++ Standards Committee Library Working Group, membership has expanded to include thousands of members of the C++ community at large.

Maintainer Bugowner

Daixtrose is a C++ header library framework that serves as a generic
disambiguated expression template (ET) core engine. It was designed to help
You to build Your own expression template library at home. In addition to
that Daixtrose comes with a full featured sparse and fixed sized
matrix/vector library which serves as a demo for the power of the new
approach and which can be used without worrying about all the gory details
of ET programming.

Maintainer Bugowner

libaosd is an advanced on screen display library. It supports many modern
features like anti-aliased text and composited rendering via XComposite, as
well as support for rendering Cairo and Pango layouts.

The netcdf package

Maintainer Bugowner

Git merge driver for ChangeLog files.

1. It produces no conflict when ChangeLog entries have been inserted
at the top both in the public and in the private modification. It
puts the privately added entries above the publicly added entries.

2. It respects the structure of ChangeLog files: entries are not split
into lines but kept together.

3. It also handles the case of small modifications of past ChangeLog
entries, or of removed ChangeLog entries: they are merged as one
would expect it.

4. Conflicts are presented at the top of the file, rather than where
they occurred, so that the user will see them immediately. (Unlike
for source code written in some programming language, conflict markers
that are located several hundreds lines from the top will not cause
any syntax error and therefore would be likely to remain unnoticed.)

Maintainer Bugowner

Cxref is a program that will produce documentation (in LaTeX, HTML, RTF or SGML)
including cross-references from C program source code.

Works for ANSI C, including most gcc extensions.

The documentation for the program is produced from comments in the code that
are appropriately formatted. The cross referencing comes from the code itself
and requires no extra work.

The documentation is produced for each of the following:

Files - A comment that applies to the whole file.
Functions - A comment for the function, including a description of
each of the arguments and the return value.
Variables - A comment for each of a group of variables and/or
individual variables.
#include - A comment for each included file.
#define - A comment for each pre-processor symbol definition, and
for macro arguments.
Type definitions - A comment for each defined type and for each element of a
structure or union type.

Any or all of these comments can be present in suitable places in the
source code.

The cross referencing is performed for the following items

Files - The files that the current file is included in
(even when included via other files).

#includes - Files included in the current file.
- Files included by these files etc.

Variables - The location of the definition of external variables.
- The files that have visibility of global variables.
- The files / functions that use the variable.

Functions - The file that the function is prototyped in.
- The functions that the function calls.
- The functions that call the function.
- The files and functions that reference the function.
- The variables that are used in the function.

Each of these items is cross referenced in the output.

Includes extensive README and FAQ with details and examples on how to use the
program.

Author
------

Andrew M. Bishop

Bugowner

NOTE: Automatically created during Factory devel project migration by admin.

Maintainer

Tools for managing filesystems, filesystem bindings or FUSE-related packages.

openSUSE Build Service is sponsored by