[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Bug#711212: ITP: libfastutil-java -- Java API providing type-specific maps, sets, lists and queues



Package: wnpp
Severity: wishlist
Owner: Andreas Tille <tille@debian.org>

* Package name    : libfastutil-java
  Version         : 6.5.4
  Upstream Author : Sebastiano Vigna <vigna@acm.org>
* URL             : http://fastutil.di.unimi.it/
* License         : Apache-2.0, LGP
  Programming Lang: Java
  Description     : Java API providing type-specific maps, sets, lists and queues
 Fastutil extends the Java™ Collections Framework by providing
 type-specific maps, sets, lists and queues with a small memory footprint
 and fast access and insertion; provides also big (64-bit) arrays, sets
 and lists, and fast, practical I/O classes for binary and text files.
 .
 The classes implement their standard counterpart interface (e.g., Map
 for maps) and can be plugged into existing code. Moreover, they provide
 additional features (such as bidirectional iterators) that are not
 available in the standard classes.
 .
 Besides objects and primitive types, fastutil classes provide support
 for references, that is, objects that are compared using the equality
 operator rather than the equals() method.


Remark: I have basically finished the lintian clean packaging and moved
the debian/ dir to

    http://people.debian.org/~tille/packages/libfastutil-java/

In the packaging I used Debian Med team as maintainer which is motivated
by the following reasons:

  1. It is a precondition for one of the Debian Med targets (goby) as
     explained here
      https://lists.debian.org/debian-med/2013/02/msg00152.html
  2. If I would stay the only Uploader it would make sense to keep
     it here because I'm watching this team very closely

However, I honestly think that the packaging should rather be done
inside the Debian Java team and I'm perfectly fine to move the
package in their repository (I can cope with Git and SVN - whatever
is prefered).  I hope that ACLs are set for DDs so I can commit
straight to this dir.  Is there any document that describes things
I should know about this team.

The third option would be to move the package into
   Debian GIS Project <pkg-grass-devel@lists.alioth.debian.org>
team because my basic motivation to create the package was rather
not the precondition for goby but rather to update mkgmap (that's
why bug #580170 is in CC).

As a last resort I would use collab-maint (which would be the less
prefered option for me).

What do you think?

In any case if you want to become an Uploader of the package and want to
share the maintenance that's more than welcome.

Kind regards

       Andreas.


Reply to: