Re: Requests to sponsor new library packages
Sune Vuorela <firstname.lastname@example.org> writes:
> On 2009-08-19, Ben Finney <email@example.com> wrote:
> > That's interesting, thank you for that perspective. What do you
> > propose, then, for a maintainer who wants to get a new package into
> > Debian, but that package requires one or more separately-packaged
> > libraries that *also* need to be sponsored into Debian before the
> > ???interesting??? package can go in?
> Request sponsorship together. And read up on library packaging.
Matthew Palmer <firstname.lastname@example.org> writes:
> Put them all into the same (or linked) RFS.
I obviously wasn't clear on this point: The library package is prepared
*first*, to provide functionality needed by the dependent package.
They're not ready for sponsorship together. What advice then?
In my case, ‘fooapp’ needs ‘libbar’, which in turn needs ‘libbaz’. So,
with only a limited amount of time, I work first on ‘libbaz’, and that
package is ready for sponsorship before the others. Should I wait until
all three are done — an indeterminate amount of time — before making an
RFS for the ready-to-inspect ‘libbaz’?
\ “It has yet to be proven that intelligence has any survival |
`\ value.” —Arthur C. Clarke, 2000 |