Bug#533708: ITP: libhugetlbfs -- Tools and Library access huge pages of memory
Hello Vincent,
On Tue, 2010-03-23 at 09:08 +0100, Vincent Danjean wrote:
> On 23/03/2010 01:20, Frank Lin PIAT wrote:
> > 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).
>
> I'm willing to co-maintain : I (will) use this software at work and I have
> already wrote and packaged library, so I can help you on this point.
Thank you for volunteering to co-maintain this package.
As you probably already noticed, I used git for the packaging, which
repository is hosted on Alioth and managed "by collab-maint group". The
package itself is Debian source v3, using debhelper v7.
Let me know if you have different preferences.
> I did not yet look at yours but can you
> tell me if you followed upstream and create bi-arch packages (ie amd64 has
> a 64bits and 32bits version for example) or if you want to go through
> the multi-arch path (I think it is a better long-term solution)
Currently, I am forcing to build in native mode only. But as I
mentioned, C and libraries are a bit like Klingon to me. All your ideas
are welcome, feel free to implement them.
For communication, I like Jonas Smedegaard's idea to use
$packagename@packages.debian.org as a pseudo mailing list. I am not
often on IRC, but you can ping me there, and I'll come back to you
(within two or three days ;). My nickname is... franklin
I am not always going to discuss very much of what I am doing and how I
am going to do it. I use VCS like a wiki: any change can be discussed,
improved or reverted. I usually tell about my TODO list by email (which
is currently up to date in the debian folder).
I have added you to the list of maintainers of the package.
We can maintain the package together (I am not "owning" the package in
any way).
Welcome on board,
Franklin
Reply to: