Re: Requests to sponsor new library packages (was: why?)

2009-08-19 Thread Matthew Palmer
On Wed, Aug 19, 2009 at 10:11:12AM +1000, Ben Finney wrote: > Sune Vuorela writes: > > For example, I would be very reluctant to sponsor a first package of a > > person that was a new library without any application using it, > > whereas a interesting kde application might easier catch my eye. >

Re: Requests to sponsor new library packages (was: why?)

2009-08-18 Thread Sune Vuorela
On 2009-08-19, Ben Finney wrote: > Sune Vuorela writes: > >> For example, I would be very reluctant to sponsor a first package of a >> person that was a new library without any application using it, >> whereas a interesting kde application might easier catch my eye. > > That's interesting, thank

Re: Requests to sponsor new library packages (was: why?)

2009-08-18 Thread Paul Wise
2009/8/19 Peter Pentchev : > I've had to do this with Perl modules once - I wanted to package > a particular module, but it had a chain of dependencies that were > not packaged yet.  What I did was file a series of ITP bugs, > stating my intentions clearly - first for the "target" package, > sayin

Re: Requests to sponsor new library packages (was: why?)

2009-08-18 Thread Peter Pentchev
On Wed, Aug 19, 2009 at 10:11:12AM +1000, Ben Finney wrote: > Sune Vuorela writes: > > > For example, I would be very reluctant to sponsor a first package of a > > person that was a new library without any application using it, > > whereas a interesting kde application might easier catch my eye.

Requests to sponsor new library packages (was: why?)

2009-08-18 Thread Ben Finney
Sune Vuorela writes: > For example, I would be very reluctant to sponsor a first package of a > person that was a new library without any application using it, > whereas a interesting kde application might easier catch my eye. That's interesting, thank you for that perspective. What do you propo