Bastian Blank <wa...@debian.org> writes:
> On Sat, Jan 15, 2011 at 01:23:01PM +0100, Julien Cristau wrote:
>> On Sat, Jan 15, 2011 at 12:21:52 +0100, Stéphane Glondu wrote:
>> > Le 15/01/2011 11:29, Philipp Kern a écrit :
>> > > Arch:all binNMUing will only work if you keep the invariant of
>> > > version(arch:all) = version(source) in some way.
>> > Why is this needed?
>> If ${source:Version} is not version(arch:all) you've got yourself an
>> uninstallable package. If ${source:Version} is not version(source)
>> things become slightly confusing.
>
> Only if it is used. However the packages in question _don't_ have
> versioned relations at all:
>
> | Package: libghc6-zip-archive-doc
> | Priority: extra
> | Section: doc
> | Installed-Size: 252
> | Maintainer: Debian Haskell Group
> <pkg-haskell-maintain...@lists.alioth.debian.org>
> | Architecture: all
> | Recommends: ghc6-doc
> | Suggests: libghc6-zip-archive-dev
>
>> Again. We've had enough of that with
>> ${Source-Version}. And it'll probably break some other stuff as well.
>
> Well. Who spoke about a change of source:Version at all?
>
> Bastian
Bringing up package relationships raises an interesting point.
If the generated docs don't work with different ghc versions then they
need to depend on the right ghc version, break the wrong version or ghc
needs to break them. I think the best would be a versioned provides
(when will they finally be usable?) like this:
Package: libghc6-zip-archive-doc
Provides: ghc6-docs (x.y)
Package: ghc6
Breaks: ghc6-docs (<< x.y), ghc6-docs (>> x.y)
But having some generated html files depend on the exact ghc version
seems extrem. So splitting out the version dependent .haddoc files into
the -dev packages (as mentioned in another mail in this thread) seems
the right, or at least the sanest, thing to do.
Am I right that with that split the -dev package depends on the right
ghc version (which is needs to anyway) while the -doc remains
independent? And with the -dev package being arch:any the whole issue of
arch:all binNMUs becomes mood?
MfG
Goswin
--
To UNSUBSCRIBE, email to debian-devel-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive: http://lists.debian.org/87r5bz6bfo.fsf@frosties.localnet
