Henning Makholm <[EMAIL PROTECTED]> writes: > Scripsit Jens Peter Secher <[EMAIL PROTECTED]> > > > But the advice in the library packaging guide is to do something like > > Package: libpackage2-dev > > Provides: libpackage-dev > > Conflicts: libpackage-dev > > AFAICT the above approach offers nothing more than simply > > Package: libpackage-dev > > would do. Right? > > If the source-level API differs, then having libpackage2-dev will > allow other packages to Build-Depend on the API they are written > against. Of course this is especially relevant when the API change can > make things break silently, but even outside that case, an explicit > build-dependency is easier to diagnose (and/or search for mechanically > over all packages in testing, say) than sudden compiler failures.
But that problem could just as well be solved by versioned build-dependency on the -dev package, right? -- Jens Peter Secher _DD6A 05B0 174E BFB2 D4D9 B52E 0EE5 978A FE63 E8A1 jpsecher get2net dk_ -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]