[prev in list] [next in list] [prev in thread] [next in thread] 

List:       kde-core-devel
Subject:    Re: Blacklisting of PIM from the CI system
From:       Harald Sitter <sitter () kde ! org>
Date:       2019-12-05 11:23:55
Message-ID: CAEc+18HjTcRwf4SR5NautKAT8FWfdDar3vNT+pkFBxdM76w6zQ () mail ! gmail ! com
[Download RAW message or body]

The point is not to do a version compare against it, but to have the
actually available sha reported in the build logs.

e.g. cmake reports
```
-- Found KF5I18n:
/usr/lib/x86_64-linux-gnu/cmake/KF5I18n/KF5I18nConfig.cmake (found
version "5.64.0.abcd123")
```

On Thu, Dec 5, 2019 at 1:23 AM Kevin Kofler <kevin.kofler@chello.at> wrote:
>
> Harald Sitter wrote:
> > Random thought to make dependency problems more obvious: glue the git
> > sha into the cmake package version for frameworks (when built from
> > git) so it finds "5.65.0.abcd123" given us a lead on what is actually
> > available.
>
> The git SHA is not going to work for this, because it is not monotonic. What
> you really want to know is whether you have something >= 5.65.0.abcd123, and
> having a 5.65.0.commithash version is not going to tell you that.
>
>         Kevin Kofler
>
[prev in list] [next in list] [prev in thread] [next in thread]