On 2009-08-19, Ben Finney ben+deb...@benfinney.id.au wrote:
Sune Vuorela nos...@vuorela.dk 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
On Wed, Aug 19, 2009 at 10:11:12AM +1000, Ben Finney wrote:
Sune Vuorela nos...@vuorela.dk 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
Sune Vuorela nos...@vuorela.dk 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.
On Wed, Aug 19, 2009 at 10:11:12AM +1000, Ben Finney wrote:
Sune Vuorela nos...@vuorela.dk 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
2009/8/19 Peter Pentchev r...@ringlet.net:
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
5 matches
Mail list logo
