Bug#533708: ITP: libhugetlbfs -- Tools and Library access huge pages of memory

[Frank Lin PIAT <fpiat@klabs.be>]

Hello Christopher and all,

This ITP was stalled, so I packaged this tool. I am looking for one or
more co-maintainer (read more at the bottom).

On Fri, 2009-06-19 at 15:18 -0700, Simmons, Christopher wrote:
> Package: wnpp
>  
> I wish to work on creating a debian package for libhugetlbfs-2.4

* Package name    : libhugetlbfs
  Version         : 2.7
  Upstream Authors: Eric B Munson <ebmunson@us.ibm.com>
                  : Adam Litke <agl@us.ibm.com>
                  : David Gibson <dwg@au1.ibm.com>
* URL             : http://libhugetlbfs.sourceforge.net/
* License         : LGPL-2.1
  Programming Lang: C
  Description     : Tools and Library access huge pages of memory

::libhugetlbfs::
Description: A library which provides access to huge pages of memory
 libhugetlbfs is a library which provides easy access to huge pages of
 memory. It is a wrapper for the hugetlbfs file system. Applications 
 can use huge pages to fulfill malloc() requests without being
 recompiled by using LD_PRELOAD. Alternatively, applications can be
 linked against libhugetlbfs without source modifications to load BSS
 or BSS, data, and text segments into large pages.

::hugepages::
Description: A set of tools to configure huge pages of memory
 This package contains a number of utilities that will help administrate
 the use of huge pages on your system.  hugeedit modifies binaries to
 set default segment remapping behavior. hugectl sets environment
 variables for using huge pages and then execs the target program.
 hugeadm gives easy access to huge page pool size control. pagesize
 lists page sizes available on the machine.


My current work is available from:
 http://git.debian.org/?p=collab-maint/libhugetlbfs.git


Co-maintainer wanted
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨
I am looking for a co-maintainer for this package. There are two reasons
for that: 1) I can't write C, well not really.  2) I believe that every
package should be co-maintained (in a perfect world anyway).

You should be prepared to handle all the aspects of the packaging which
are specific to C and/or library handling. I can help for other aspects
of packaging, bug handling, backporting patches, etc...

Current Lintian :
> P: libhuge*: no-upstream-changelog
> W: libhugetlbfs*: shlib-without-versioned-soname ...
> E: libhugetlbfs: postinst-must-call-ldconfig 

Regards,

Franklin