>
>  libqt4-dev 4.1 is short-lived ancient history, and doesn't exist on any
>  Debian distribution: sarge (oldstable) doesn't have any libqt4-dev, and
>  etch (stable), lenny (testing), and sid (unstable) all have 4.2 or above.
>  Even at the time this bug was originally, there was no libqt4-dev < 4.2 out
>  there for any Debian distribution.
>
>  Debian is a universal *distribution*, but that doesn't mean that packages
>  can or should always magically work on any derived or backported
>  distribution. Someone could argue that *every* dependency needs to be
>  versioned, since there are ancient versions of just about every library
>  that aren't compatible with that is currently being used.
>
>  The bottom line is, this is not a bug in the Debian package, but is either
>  causing you some grief in some derivitive distribution, or you are mixing
>  and matching packages from different distributions. In the first case, I
>  suggest that you file a bug with the actual distribution you are using

Then the derivative (e.g. Ubuntu) should eventually contribute this
fix back to Debian upstream?

>  (e.g. Ubunutu). In the second case, mixing packages from different
>  distributions is always at-your-own-risk.

Yes, "at-my-own-risk" also mean that I should find out the solution by myself.
And now, I'm willing to contribute the solution back to Debian.
Will Debian never accept the contributed solution for the unsupported things?

>
>  Anyway, sorry to rant a bit, but I already closed this bug with this same
>  justification more than a year ago. You seemed happy with it then, but now

No, I just wait for your response.
http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=386291#15

>  you've dredged it back up from the archives and reopened it.
>
>  If I'm misunderstanding your use-case here, please explain it to me in more
>  detail. I am truly interested in fixing bugs, but I'm not interested in
>  makework to help do explicitly unsupported things.
>

Apart from the solution specific to Debian packaging.
The mimms software by itself (when act as the upstream software, not
debian software), should have some mechanism to check for qt version
(e.g. configure script), or at least have some hint about qt version
in README/INSTALL file.

PS. Thanks for your kindly unsupported suggestion (about qt version)
on unsupported things.



-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Reply via email to