On Tue, May 24, 2005 at 11:30:05PM +0200, Agustin Martin wrote: > On Tue, May 24, 2005 at 03:13:41PM +0200, Matthias Klose wrote: > > Package: aspell > > > > Many aspell dictionaries depend on the libaspell15 package. with the > > next soversion (or the coming C++ ABI change), the package name has to > > be changed, as well as other 24 dictionary packages. That's just a > > maintainance burden. Package dictionaries may depend on aspell (>= > > 0.60) instead, but you may argue, that the aspell binary isn't > > necessarily needed. Proposing: > > > > - a new libaspell package, which depends on the current libaspell15 > > package (a provides is not enough, because dictionaries have to > > depend on an version, and versioned provides don't yet exist) > > > > - alternatively dictionary packages should depend on aspell. > > > > - a short paragraph in README.Debian as a mini policy. > > Just to note that after Brian suggestion, one of the things that are waiting > in dictionaries-common for sarge release is aspell-autobuidhash, allowing the > binary hashes being built from dict postinst. This is still very > experimental, and would require for dicts using it that not only libaspellxx > is installed but also aspell-bin, but should make dependencies simpler for > those dicts, since the dependency would be on aspell-bin, which is synced to > the appropriate libaspellxx because it depends on it.
Yeah, what he said. Couple questions: Matthias: How soon will the C++ ABI transition start? Or, in other words, how long do we have to implement the autobuildhash for all of the dictionaries before the libaspell name will have to change? Agustin: What's the status of aspell-autobuildhash? I'd like to start seriously testing it very soon, within the next couple of weeks, so that we can start transitioning the dictionary packages as soon as sarge releases. -- Society is never going to make any progress until we all learn to pretend to like each other. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
