On Mon, Jun 13, 2005 at 05:43:50PM +0200, Sven Luther wrote: > On Mon, Jun 13, 2005 at 01:51:23AM -0700, Steve Langasek wrote: > > On Mon, Jun 13, 2005 at 10:15:30AM +0200, Stefano Zacchiroli wrote: > > > [ Mail-Followup-To: set to debian-mentors only ] > > > On Mon, Jun 13, 2005 at 09:57:25AM +0200, Goswin von Brederlow wrote: > > > > You can't Build-Depend on virtual packages. > > > Ok, time to settle down this issue. > > > We do, all ocaml packages build depends on ocaml-3.08.3 a virtual > > > package provided by ocaml. What's the problem with that? It has worked > > > properly for two years or so. > > Then you've been lucky. I don't think I've ever seen a clear statement that > > virtual build dependencies *should* work, but they usually *do* work -- > > *except* when there are bugs, which has happened from time to time. It > > seems that sbuild particularly likes to object to build-dependencies on > > virtual packages that were once real packages (e.g., libmysqlclient-dev -> > > libmysqlclient12-dev). As a result, it seems to generally be more robust to > > build-dep on a real package when possible. > Let's make them working a etch release goal, ok ? What would be the point of that? I've already noted that this is supported; it just hasn't been supported consistently enough over time and across all buildds to allow people to depend on it 100%. What would the release goal here be: "sbuild must never again have bugs that break build-deps on virtual packages"? You're welcome to work with the sbuild maintainers to make its handling of virtual build-deps more robust; but the release goal is "packages must build from source", and I don't see any reason that needs to be expanded here. -- Steve Langasek postmodern programmer
Attachment:
signature.asc
Description: Digital signature