Re: RFS: v3c + treedb + meta-treedb + v3c-dcom + v3c-qt + v3c-qt-examples
Dear mentors,
I am looking for a sponsor for the v3c, treedb, meta-treedb, v3c-dcom,
v3c-qt
and v3c-qt-examples packages, details below.
They form the following build dependency tree:
v3c
|- treedb
| \- meta-treedb
| \- v3c-dcom
\- v3c-qt
\- v3c-qt-examples
Because they have similar structure, I believe that a single sponsor
would be
able to review these packages much more efficiently than separately - the
similarity of their structure should become clear after looking at two
or more
packages.
I used pbuilder to build them and the lintian checks issue only warnings.
I used a bind mount to a local repository where pbuilder stored the
generated
packages.
I used the same directory to install the packages locally once pbuilder had
built them, after regenerating the Packages file and running
apt-get-update.
Then I built the dependent package from its local GIT repo and then ran the
pbuilder build.
Finally I signed the .dsc and .changes files for the package files that
pbuilder
output and dput them to mentors.
--------------------------------------------------------------------------------
name: v3c
version: 2.5.0-01
upstream url: http://sourceforge.net/projects/v3c/
dsc file:
http://mentors.debian.net/debian/pool/main/v/v3c/v3c_2.5.0-01-1.dsc
git repo: git://v3c.git.sourceforge.net/gitroot/v3c/v3c (read-only)
license: LGPLv3
section: devel
short description: v3c utility toolkit
long description:
v3c is a build framework that ties in with GNU make, providing
"boilerplate" code for the most common use cases of building
software.
.
Among its capabilities are doxygen documentation integration, Git version
control integration, configurable build modes (for debug and release
builds,
for example), and the ability to specify most configurable options in the
top-level makefile.
It also provides a general purpose C++ class library for use in client
projects.
.
See treedb, meta-treedb, v3c-dcom and v3c-qt as examples of projects
that use
the v3c build framework.
packages built:
* v3c (program + library + package build helpers)
* v3c-dev (library dev)
* v3c-dbg (debugging symbols)
* v3c-doc (Doxygen generated documentation)
--------------------------------------------------------------------------------
name: treedb
version: 1.3.0-01
upstream url: http://sourceforge.net/projects/treedb/
dsc file:
http://mentors.debian.net/debian/pool/main/t/treedb/treedb_1.3.0-01-1.dsc
git repo: git://v3c.git.sourceforge.net/gitroot/treedb/treedb (read-only)
license: LGPLv3
section: devel
short description: on-disk memory library
long description:
treedb can implement malloc functionality, and much more!
Need a heap that allocates of a fixed size chunk of memory? No problem.
But where treedb comes into its own is when it comes to allocating from a
mmap()ed disk file - the memory becomes persistent.
.
If you follow the tests/examples, you too can store dictionaries,
trees, lists
or whatever you can think of in disk-based memory, just an open() and
mmap()
away.
.
Treedb comes with an AVL tree, doubly-linked-list and
variable-entry-sized-array
implementations for you to use in your data structures.
packages built:
* treedb (programs + library + package build helpers)
* treedb-dev (library dev)
* treedb-dbg (debugging symbols)
* treedb-doc (Doxygen generated documentation)
--------------------------------------------------------------------------------
name: meta-treedb
version: 1.4.0-01
upstream url: http://sourceforge.net/projects/meta-treedb/
dsc file:
http://mentors.debian.net/debian/pool/main/m/meta-treedb/meta-treedb_1.4.0-01-1.dsc
git repo: git://v3c.git.sourceforge.net/gitroot/treedb/treedb (read-only)
license: LGPLv3
section: devel
short description: on-disk memory library using meta-data
long description:
meta-treedb can implement malloc functionality, and much more!
Need a heap that allocates of a fixed size chunk of memory? No problem.
But where treedb comes into its own is when it comes to allocating from a
mmap()ed disk file - the memory becomes persistent.
.
If you follow the tests/examples, you too can store dictionaries,
trees, lists
or whatever you can think of in disk-based memory, just an open() and
mmap()
away.
.
Meta-treedb comes with an AVL tree, doubly-linked-list and
variable-entry-sized-array implementations for you to use in your data
structures.
.
So, what distinguishes meta-treedb from treedb?
* "class" interfaces for treedb collections
. These are vtables (virtual function tables) that implement the
interface.
* faster compiles - only the "class" interfaces are visible to client code
. This is at the expense of a small performance hit.
* the ability to use implementations that were developed after client
code was
. compiled.
. This feature hasn't been fully fleshed out yet, as it would require a
. plug-in system such as that provided by v3c-dcom, but it's coming soon.
packages built:
* meta-treedb (programs + library + package build helpers)
* meta-treedb-dev (library dev)
* meta-treedb-dbg (debugging symbols)
* meta-treedb-doc (Doxygen generated documentation)
--------------------------------------------------------------------------------
name: v3c-dcom
version: 1.3.0-01
upstream url: http://sourceforge.net/projects/v3c-dcom/
dsc file:
http://mentors.debian.net/debian/pool/main/v/v3c-dcom/v3c-dcom_0.5.0-01-1.dsc
git repo: git://v3c.git.sourceforge.net/gitroot/v3c-dcom/v3c-dcom
(read-only)
license: LGPLv3
section: devel
short description: Baby steps to DCOM
long description:
v3c-dcom provides a plug-in system as an alternative COM implementation.
Unlike COM, v3c-dcom encourages the use of "sandboxes" of registered
plug-ins,
so allowing per site, per-group, per-user, per-program and per-job
sandboxes,
allowing virtually unlimited configuration and customization.
Users and client programs can even create sandboxes on the fly.
.
Using COM's naming scheme aims at reducing the learning curve for those
familiar with COM, as does the tiny ATL implementation for C++ developers.
packages built:
* v3c-dcom (programs + library + package build helpers)
* v3c-dcom-dev (library dev)
* v3c-dcom-dbg (debugging symbols)
* v3c-dcom-doc (Doxygen generated documentation)
--------------------------------------------------------------------------------
name: v3c-qt
version: 0.7.0-01
upstream url: http://sourceforge.net/projects/v3c-qt/
dsc file:
http://mentors.debian.net/debian/pool/main/v/v3c-qt/v3c-qt_0.7.0-01-1.dsc
git repo: git://v3c.git.sourceforge.net/gitroot/v3c-qt/v3c-qt (read-only)
license: LGPLv3
section: devel
short description: v3c/automake wrapper for Qt4
long description:
The v3c-qt package ties Qt doxygen-generated documentation into the v3c
documentation chain, so that client packages can "inherit" this in
their own
doxygen-generated documentation.
.
It also provides automake rules for MOC, UIC and RCC, to ease their
usage in
the automake Makefile.am files of client projects.
packages built:
* v3c-qt (package build helpers)
* v3c-qt-doc (Doxygen generated documentation)
--------------------------------------------------------------------------------
name: v3c-qt-examples
version: 0.7.0-01
upstream url: http://sourceforge.net/projects/v3c-qt/
dsc file:
http://mentors.debian.net/debian/pool/main/v/v3c-qt-examples/v3c-qt-examples_0.7.0-01-1.dsc
git repo: git://v3c.git.sourceforge.net/gitroot/v3c-qt/examples (read-only)
license: LGPLv3
section: devel
short description: v3c/automake wrapper for Qt4 - examples
long description:
The v3c-qt package ties Qt doxygen-generated documentation into the v3c
documentation chain, so that client packages can "inherit" this in
their own
doxygen-generated documentation.
.
It also provides automake rules for MOC, UIC and RCC, to ease their
usage in
the automake Makefile.am files of client projects.
.
This is the examples package.
packages built:
* v3c-qt-examples (programs)
* v3c-qt-examples-dbg (debugging symbols)
* v3c-qt-examples-doc (Doxygen generated documentation)
--------------------------------------------------------------------------------
I would be glad if someone could review then upload these packages for me.
Regards,
Philip Ashmore
Reply to: