On 2024-05-24 16:39 +0200, David Given wrote: > I'm try to put together a package for a big, complex application. One of > its dependencies isn't in Debian yet. What do I do?
Package the dependency first. > - package up the dependency and somehow get both packages sponsored at the > same time (how?); > - package up the dependency and get it sponsored first... meaning that I'll > be trying to get a library added which has no users. This is what I do. All packages have no users before they enter the archive so that's not really a problem. I quite often find that there in fact other packages using a library in the archive but they've bundled it (because that's easier and is often what upstream has done). So a 3rd step is to file patches for those other packages to use your library. sources.debian.org is a good place to look for such instances. You can do both at once but I find it easier if the libraries go in first, then you can be sure everything works without having to have 'special' build environment with your extra library packages present. Mostly it depends how fast you want to move. Either is fine. Wookey -- Principal hats: Debian, Wookware, ARM http://wookware.org/
signature.asc
Description: PGP signature
